sessionpipe 0.9.0 → 0.10.0

package/README.md

@@ -92,7 +92,13 @@ Permission prompts can be answered from the receiver too: while the terminal sho
 its prompt, the PermissionRequest hook waits for your signed answer, and whichever
 comes first wins. Nothing is ever auto-allowed. Safe mode (the default) runs headless
 turns with `--permission-mode dontAsk`, so nothing that needs approval runs while
-you're away.
+you're away. Auto mode runs them with `--permission-mode auto`; where Claude Code's
+settings turn auto mode off (`permissions.disableAutoMode`), Claude Code runs them in
+its default mode instead, which refuses whatever needs approval. Inherit mode
+(`sessionpipe control mode inherit`, chosen only at the machine) passes no permission
+flag, so each turn starts in the mode Claude Code picks by itself there, its
+settings' `permissions.defaultMode`: messaged sessions run the way your own do,
+`bypassPermissions` included if that is what you set.
 
 Codex and Antigravity sessions are reached headlessly too, when `codex` or `agy` is
 installed (the daemon looks on PATH, beside its own Node, in `~/.local/bin`, or where
@@ -101,7 +107,9 @@ installed (the daemon looks on PATH, beside its own Node, in `~/.local/bin`, or
 message is `codex exec resume <thread>` or `agy --conversation <id>`. Safe mode runs
 Codex in its `workspace-write` sandbox and agy with no permission flag (it denies, and
 the reply lists, what it wasn't allowed to do); auto mode passes `--approve-for-me` /
-`--mode accept-edits`. The bypass flags are never passed. Both CLIs pick a new
+`--mode accept-edits`; inherit mode passes no flag, so Codex follows the
+`approval_policy` and `sandbox_mode` in your `config.toml`. The bypass flags are never
+passed. Both CLIs pick a new
 session's id themselves, so the daemon keeps the one your start named: it records the
 pair in `~/.local/state/sessionpipe/control/aliases.json`, and your receiver keeps
 seeing one session under one id. A message to a Codex session someone has open (its
@@ -109,6 +117,21 @@ rollout written in the last 90 seconds) is acked `unsupported` rather than resum
 Before a Codex run the daemon checks `codex login status` (or `CODEX_API_KEY`) and says
 `codex login --device-auth` if it isn't signed in.
 
+Any other agent that speaks the [Agent Client Protocol](https://agentclientprotocol.com)
+is reached the same way: Gemini CLI, OpenCode, goose, Copilot CLI, Cursor, Droid, Devin,
+Kilo, Qwen Code, Cline and the rest of the ACP registry ([the list, with each one's
+launch line](../../spec/ADAPTERS.md#agents-driven-through-acp-control-only)). The daemon
+runs the agent's own CLI (`gemini --acp`, `opencode acp`, …) when it is installed, on
+PATH or where `SESSIONPIPE_ACP_<HARNESS>` points (`SESSIONPIPE_ACP_GEMINI_CLI`), and
+never downloads one. It is the agent's client: a start opens a session in your folder,
+the reply streams back as the agent writes it, and the process stays up so the next
+message lands in it with no cold start (`api` mode); `cancel` works there too. An agent
+idle for ten minutes is closed, and a later message reopens the session where the agent
+supports `session/load`. Safe mode answers every permission the agent asks with a
+refusal, listed in the reply; auto mode allows. An agent that never asks (OpenCode, by
+its own settings) runs its tools as it would at your terminal. Signing in is yours to do
+at the terminal: an agent that wants it says so in the reply.
+
 ## Updates
 
 The control daemon keeps its own copy current. About a minute after it starts, and then