2.0 KiB
Chat backends
Chats can be created on more than one harness. OpenCode remains the default;
Codex is available when its App Server control socket exists. The selected
backend is stored on the operator-session row and returned as backend on every
chat_sessions row, so a restart does not have to guess from the session id.
Codex
The adapter in internal/codex connects to the Codex App Server's Unix
WebSocket control socket ($CODEX_HOME/app-server-control/app-server-control.sock,
falling back to ~/.codex). It uses the operator's existing Codex login. A new
chat issues thread/start; a prompt issues turn/start; history comes from
thread/read; questions map from item/tool/requestUserInput to the normal
question card and chat_answer returns the JSON-RPC response. Threads created
this way are ordinary Codex threads and remain visible to the Codex app.
New threads retain the workspace-write sandbox and inherit Codex's configured
approval policy (Pipelines no longer forces never). Command, file-change,
network and explicit permission requests appear in the web approval cards. Each
JSON-RPC callback has its own identity, including Code Mode subcommands sharing
one item. Allow once maps to accept, session grants to acceptForSession, and
Reject to decline; explicit permission profiles grant only requested fields.
The web labels session scope explicitly, never as a permanent policy change.
Pending questions and approvals survive browser reconnects while the App Server connection lives. Standard MCP form/URL elicitation supports typed answers, Accept/Decline/Cancel and safe external links. Extended OpenAI elicitation is not advertised; unknown request formats return an explicit unsupported RPC error, not a fake empty success or silent auto-approval. App Server socket loss does not provide durable callback recovery; a disconnected transport is reported as an error rather than claiming old requests are still actionable.
Claude is not advertised as a backend until its sidecar and login flow are wired.