zooid 0.13.0 → 0.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -32,7 +32,7 @@ zooid init
32
32
 
33
33
  `zooid init` asks which harness (`claude`, `codex`, `opencode`, `pi`), which model provider, and how to authenticate. It writes a clean `zooid.yaml` and any `.env` it needs.
34
34
 
35
- Every preset can run off a subscription you already have instead of a fresh API key. `pi` goes a step further: it only offers that choice once it has actually found a `pi` login, inherits the `defaultProvider` / `defaultModel` you already run, and gives the agent its own relocated config dir (`.pi-agent/`) so it never writes into your `~/.pi`.
35
+ Every preset can run off a subscription you already have instead of a fresh API key.
36
36
 
37
37
  Boot the local stack:
38
38
 
@@ -91,6 +91,11 @@ Zooid publishes a small set of base images on GHCR. Drop one into `zooid.yaml` u
91
91
  - `ghcr.io/zooid-ai/agent-opencode` — agent-base + opencode.
92
92
  - `ghcr.io/zooid-ai/agent-pi` — agent-base + pi + pi-acp.
93
93
 
94
+ Pi does not expose MCP servers. When a Pi agent starts, Zooid installs its
95
+ native extension at `~/.pi/agent/extensions/zooid-tasks.js`; it gives the agent
96
+ the `zooid_*` room-reading and task tools while preserving any operator-owned
97
+ extensions already in that directory.
98
+
94
99
  The persona — `CLAUDE.md` / `AGENTS.md`, `.claude/settings.json`, skills, MCP servers — lives in the agent's `workdir` on the host. Zooid bind-mounts that directory into the container at runtime, so the shim picks it up the same way it would on your laptop. No `docker build`, no custom image, no rebuild when you tweak instructions.
95
100
 
96
101
  ## Contributing