Be honest about which install commands I could not verify

I have no grok CLI on this machine, so `grok plugin marketplace add` is taken from
the docs rather than run. Say so, point at the TUI's Marketplace tab as the route
that does not depend on a subcommand name, and note that the plain clone into
~/.grok/plugins/ needs none of it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
iceBear67
2026-08-09 07:34:06 +00:00
co-authored by Claude Opus 5
parent 3cfa011d0c
commit b586323fdb
+12 -6
View File
@@ -58,18 +58,24 @@ background, and the dashboard is on `http://127.0.0.1:8791`.
### …or from a marketplace, by URL
If you would rather install it the way marketplace plugins are installed — or share it with other
machines — this repo is also its own one-entry marketplace (`.grok-plugin/marketplace.json`). Add
it as a marketplace source and install from it:
If you would rather install it the way marketplace plugins are installed — or point several
machines at one URL — this repo is also its own one-entry marketplace:
`.grok-plugin/marketplace.json` lists exactly one plugin, sourced from `./`, which is the repo
root the catalog itself lives in. So the repo's git URL is a complete marketplace, with no commit
SHA to pin (a self-referencing remote source would have to pin the SHA of the commit that contains
the pin).
Add it as a marketplace source from the TUI — `/plugins`, Marketplace tab — or from the CLI:
```sh
grok plugin marketplace add https://your-git-host/you/grok-glance.git
grok plugin install grok-glance --trust
```
Marketplace sources also live in `~/.grok/config.toml` under `[[marketplace.sources]]` and in
`~/.grok/plugins/known_marketplaces.json`, if you prefer to write them there directly. The TUI's
Marketplace tab reads the same list.
Configured sources are recorded in `~/.grok/config.toml` under `[[marketplace.sources]]` and in
`~/.grok/plugins/known_marketplaces.json`; the TUI and `grok plugin marketplace list` read the same
list. Check `grok plugin marketplace --help` if the subcommand names have moved — the clone above
does not depend on any of this.
### Why there is no build step