gaunt-sloth 2.0.0-alpha.38 → 2.0.0-alpha.39

package/README.md

@@ -63,7 +63,26 @@ For full usage documentation see the [root README](https://github.com/pukeko-rob
 can drive Gaunt Sloth as its coding agent. Point the editor's agent configuration at either
 command; it needs no arguments.
 
-**ACP v2 only.** A host that speaks only ACP v1 cannot connect. Zed speaks v2.
+**Both ACP v1 and ACP v2 are served**, and the version is taken from the host's own `initialize` —
+there is nothing to configure. v1 is the stable protocol every shipping ACP editor uses today, Zed
+included; v2 is a draft.
+
+**An ACP session runs as a coding session.** It resolves under the `code` command, so it takes its
+filesystem access, approvals posture and tools from your `commands.code` config: it can run shell
+commands, and it can edit and delete files in the directory the session was opened on.
+
+At the default approvals rung, `assisted`, the gate holds only the **shell** — a command it does not
+clear reaches the editor as a permission request. **File changes are not prompted:** the agent
+rewrites and deletes files in that directory without asking. `manual` is the rung that sends the
+file tools to the editor as well — set `"approvals": "manual"` under `commands.code` to scope that
+to editor sessions, or at the root to apply it everywhere. For a read-only editor agent instead, set
+the mode:
+
+```json
+{ "acp": { "mode": "chat" } }
+```
+
+which resolves the session under `commands.chat` instead — read-only filesystem, no shell.
 
 Files you attach to a message — an @-mention in Zed — reach the agent as a link it can open with its
 file tools. Images and audio are not accepted; if a host sends them anyway the agent says so in its

package/cli.js

@@ -11,9 +11,10 @@ process.on('warning', (warning) => {
 
 // --- ACP server ------------------------------------------------------------
 // `gaunt-sloth --acp-agent` is the ACP (Agent Client Protocol) door into the fat
-// `gaunt-sloth` package. It serves ACP v2 over stdio through the SAME startup as
-// the standalone `gaunt-sloth-acp` bin, so the two doors cannot behave
-// differently — including the redirect that keeps stdout free for JSON-RPC.
+// `gaunt-sloth` package. It serves ACP over stdio — v1 or v2, whichever the host
+// asks for — through the SAME startup as the standalone `gaunt-sloth-acp` bin, so
+// the two doors cannot behave differently, including the redirect that keeps
+// stdout free for JSON-RPC.
 //
 // The switch is handled here rather than left to fall through to the normal CLI,
 // which would answer an ACP host with a chat session on stdout and hang it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gaunt-sloth",
-  "version": "2.0.0-alpha.38",
+  "version": "2.0.0-alpha.39",
   "description": "",
   "license": "MIT",
   "author": "Andrew Kondratev",
@@ -44,11 +44,11 @@
     "@langchain/xai": "^1.4.6",
     "commander": "^15.0.0",
     "zod": "^4.4.3",
-    "@gaunt-sloth/core": "2.0.0-alpha.38",
-    "@gaunt-sloth/review": "2.0.0-alpha.38",
-    "@gaunt-sloth/batch": "2.0.0-alpha.38",
+    "@gaunt-sloth/agent": "2.0.0-alpha.39",
+    "@gaunt-sloth/batch": "2.0.0-alpha.39",
+    "@gaunt-sloth/core": "2.0.0-alpha.39",
     "@gaunt-sloth/eval-reporter-junit": "0.1.0",
-    "@gaunt-sloth/agent": "2.0.0-alpha.38"
+    "@gaunt-sloth/review": "2.0.0-alpha.39"
   },
   "optionalDependencies": {
     "chalk": "^6.0.0",