Read-only sessions a client can rely on (follow-up to #1063) #2827
Replies: 1 comment
|
I work on Open Agent API, a gateway that puts SDK-compatible HTTP endpoints in front of agents. This is useful there too: the API caller sees the same interface for different backends and cannot reasonably interpret backend-specific mode labels. I would keep the requirement separate from UI config options. In particular, read-only and tool-free are different guarantees: a read-only run might still inspect files, while a tool-free turn should not invoke tools at all. A capability can tell the client whether asking is supported, but only the response for that session should confirm that the requirement was accepted. One case I would add to the proposal is load/resume on a new connection. Should the agent echo the accepted constraint again and reject the load if it cannot restore it? That would let a gateway fail closed instead of inferring safety from the old session ID. |
Uh oh!
There was an error while loading. Please reload this page.
#1063 was closed to revisit with the orchestrator work. Is that tracked anywhere? Here is a client case for it.
I maintain via, which runs Codex (through codex-acp) and OpenCode as subagents of another coding agent. Its one hard promise is a read-only run: when the user asks for one, the agent can't change anything. ACP gives a client no way to ask for that or check it, so via works it out per agent:
read-only. Mode ids are free-form; I found this one in codex-acp's source.planmode still allows bash. via adds its own agent with every write tool denied, and turns off project config so a repo can't turn bash back on.model_configandspeedcategories, but the spec says categories must not be required for correctness.So each new agent means reading its source, and a wrong guess fails open.
What would fix it:
This doesn't ask ACP to sandbox anything; the security page rules that out. It asks for a defined name for a guarantee some agents already enforce.
Does this belong in the orchestrator work, or in config options? If config options, it would need a reserved meaning, since categories are UX only.
All reactions