chat: add the Codex backend
Store a chat's harness with its operator session, expose chat_backends and a backend choice in New chat, and route each session through a manager. The Codex adapter uses the App Server's Unix WebSocket for threads, turns, history, questions and interrupt; OpenCode remains the default and Claude is not advertised until its sidecar and login are wired.
This commit is contained in:
@@ -62,6 +62,7 @@ export const Protocol = Object.freeze({
|
||||
CHAT_REOPEN: "chat_reopen",
|
||||
CHAT_STAR: "chat_star",
|
||||
CHAT_RENAME: "chat_rename",
|
||||
CHAT_BACKENDS: "chat_backends",
|
||||
// The shared live stream (C5). `chat_subscribe` attaches this connection to one
|
||||
// session's stream (body: the session id); the server then pushes `chat_event`
|
||||
// frames without a matching request id, so every client watching a session sees
|
||||
@@ -116,6 +117,7 @@ export const ChatKeys = Object.freeze({
|
||||
EVENT: "chat_event",
|
||||
ANSWER: "chat_answer",
|
||||
RENAME: "chat_rename",
|
||||
BACKENDS: "chat_backends",
|
||||
// The composer's payloads (C8/C9). `chat_interrupt` deliberately has no key of
|
||||
// its own: its body is the same `chat_query` the other session-scoped commands
|
||||
// carry (internal/protocol/chat.go ChatQuery, Chat.kt interruptRequest), so a
|
||||
|
||||
Reference in New Issue
Block a user