docs: clarify that no extensions are installed by default
Two-line addition to docs/extensions.md and a tightening of the README bullet point. examples/extensions/* are reference code; a fresh `zot install` gives you a clean agent. Users opt in by copying examples (or any other extension) via `zot ext install` or by pointing `zot --ext PATH` at a working directory for one session. No code changes.
- commit
- 463c62daf3281a9d502f2a5ab3cf137ab4a10a99
- author
- patriceckhart · · 2026-04-19 13:23 UTC
- parent
- 7e94b07
- signature
- unsigned
2 files · +20 -1
M README.md +1 -1
| @@ -7,7 +7,7 @@ yet another coding agent harness, lightweight and written (vibe-slopped) in go. | |||
| 7 | 7 | - four tools (read, write, edit, bash). | |
| 8 | 8 | - three run modes (interactive tui, print, json). | |
| 9 | 9 | - built-in telegram bot. | |
| 10 | - | - extensions in any language via subprocess + json-rpc; see [docs/extensions.md](docs/extensions.md). | |
| 10 | + | - extensions in any language via subprocess + json-rpc — none installed by default; opt in with `zot ext install` or `zot --ext`. see [docs/extensions.md](docs/extensions.md). | |
| 11 | 11 | - reusable instructions via `SKILL.md` files; see [docs/skills.md](docs/skills.md). | |
| 12 | 12 | - no community atm. | |
| 13 | 13 | ||
| @@ -7,7 +7,7 @@ yet another coding agent harness, lightweight and written (vibe-slopped) in go. | |||||
| 7 | - four tools (read, write, edit, bash). | 7 | - four tools (read, write, edit, bash). | ||
| 8 | - three run modes (interactive tui, print, json). | 8 | - three run modes (interactive tui, print, json). | ||
| 9 | - built-in telegram bot. | 9 | - built-in telegram bot. | ||
| 10 | - | - extensions in any language via subprocess + json-rpc; see [docs/extensions.md](docs/extensions.md). | 10 | + | - extensions in any language via subprocess + json-rpc — none installed by default; opt in with `zot ext install` or `zot --ext`. see [docs/extensions.md](docs/extensions.md). |
| 11 | - reusable instructions via `SKILL.md` files; see [docs/skills.md](docs/skills.md). | 11 | - reusable instructions via `SKILL.md` files; see [docs/skills.md](docs/skills.md). | ||
| 12 | - no community atm. | 12 | - no community atm. | ||
| 13 | 13 | ||||
M docs/extensions.md +19 -0
| @@ -61,6 +61,25 @@ zot ext install ./hello-py | |||
| 61 | 61 | ||
| 62 | 62 | Restart `zot`, type `/hellopy`, the agent greets you. Done. | |
| 63 | 63 | ||
| 64 | + | ## Built-in extensions | |
| 65 | + | ||
| 66 | + | **zot ships with no extensions installed by default.** A fresh `zot install` (or `go install`) gives you a clean agent. Extensions are entirely opt-in: you install (or `--ext` for one run) only the ones you want. | |
| 67 | + | ||
| 68 | + | The `examples/extensions/` directory in the repo is reference code, not a default install set. To use any of those: | |
| 69 | + | ||
| 70 | + | ```bash | |
| 71 | + | # go-based examples need a build first | |
| 72 | + | cd path/to/zot/examples/extensions/hello && go build -o hello . | |
| 73 | + | ||
| 74 | + | # install (copies to $ZOT_HOME/extensions/hello/) | |
| 75 | + | zot ext install path/to/zot/examples/extensions/hello | |
| 76 | + | ||
| 77 | + | # or load straight from the repo for one zot session | |
| 78 | + | zot --ext path/to/zot/examples/extensions/hello | |
| 79 | + | ``` | |
| 80 | + | ||
| 81 | + | Nothing is auto-installed and nothing reaches out to the network without your explicit action. | |
| 82 | + | ||
| 64 | 83 | ## Layout & discovery | |
| 65 | 84 | ||
| 66 | 85 | zot scans two directories on startup, in this order: | |
| @@ -61,6 +61,25 @@ zot ext install ./hello-py | |||||
| 61 | 61 | ||||
| 62 | Restart `zot`, type `/hellopy`, the agent greets you. Done. | 62 | Restart `zot`, type `/hellopy`, the agent greets you. Done. | ||
| 63 | 63 | ||||
| 64 | + | ## Built-in extensions | |||
| 65 | + | ||||
| 66 | + | **zot ships with no extensions installed by default.** A fresh `zot install` (or `go install`) gives you a clean agent. Extensions are entirely opt-in: you install (or `--ext` for one run) only the ones you want. | |||
| 67 | + | ||||
| 68 | + | The `examples/extensions/` directory in the repo is reference code, not a default install set. To use any of those: | |||
| 69 | + | ||||
| 70 | + | ```bash | |||
| 71 | + | # go-based examples need a build first | |||
| 72 | + | cd path/to/zot/examples/extensions/hello && go build -o hello . | |||
| 73 | + | ||||
| 74 | + | # install (copies to $ZOT_HOME/extensions/hello/) | |||
| 75 | + | zot ext install path/to/zot/examples/extensions/hello | |||
| 76 | + | ||||
| 77 | + | # or load straight from the repo for one zot session | |||
| 78 | + | zot --ext path/to/zot/examples/extensions/hello | |||
| 79 | + | ``` | |||
| 80 | + | ||||
| 81 | + | Nothing is auto-installed and nothing reaches out to the network without your explicit action. | |||
| 82 | + | ||||
| 64 | ## Layout & discovery | 83 | ## Layout & discovery | ||
| 65 | 84 | ||||
| 66 | zot scans two directories on startup, in this order: | 85 | zot scans two directories on startup, in this order: | ||