Agent console

Hidden from the game for now. /genshin is the game alone, its opening and then its world, so it is faithful to the game with nothing of the console over it. The console's page code stays, unmounted, until it is rebuilt in the game's own style from genshin-interface; until then the link a host prints opens the game and pairs nothing.

The agent console is one page of the app, shown as Genshin at /genshin, that works the Claude Code sessions on a machine instead of the terminal: the conversation, every tool call and its result, the diffs, the permission prompts, the model, mode, context, cost and usage, subagents and the todo list, across every session on the host. It works the same sessions the terminal does. A session started here resumes with claude --resume <id>, and one started in a terminal resumes here. Nothing is lost moving between them, because both read and write the same transcripts.

It has two halves. The host, agent-console-server, runs on the machine with the code and the Claude Code login (host). The page is served by the app on the deployed site or on pnpm dev, and knows only which host it is paired with. Between them is one WebSocket carrying Zod contracts, which the page imports from the host's contracts subpath, so a change to the wire fails typecheck on both sides.

How it works

flowchart LR
  subgraph Browser
    P[The agent console page] --> C[Connection store: one socket, reconnects on its own]
    C --> S[Session store: one event log per session]
    S --> W[Genshin world and its console: the bar, conversation, composer, permission requests]
    W -->|commands| C
  end
  subgraph Host[agent-console-server, on the machine with the code]
    WS[WebSocket for paired pages, and the event log it replays] --> D{Driver}
    D -->|Claude Agent SDK| Q[One streaming-input query per open session]
    Q --> T[Transcripts where the terminal writes them]
  end
  C <-->|contracts| WS

• The event log is the only state. The host keeps each open session's events and replays them to a page that connects or reconnects. The page folds them per session, in a store keyed by session id, into everything it shows: the conversation, the timeline, the diffs, the checklist and the permission requests. An event updates only what it changes, and a reconnect that replays the log rebuilds all of it.
• The agent is behind a driver. The Claude Agent SDK driver is the one that exists. Any other agent would be one more driver behind the same interface, and never a change to the page.
• The look is behind a theme. AgentConsoleThemeMap holds the default and the Genshin theme. The default is the world and its console overlay with no character, plus a browser notification when a turn ends or a permission prompt waits while the tab is hidden. A reload replays history without ringing, because only events newer than the page's connection trigger a reaction. The Genshin theme adds an avatar: a session the persona plugin started is presented as its character, named in the heads-up display. The fold keeps the context each SessionStart hook added, and each theme looks there for its own plugin's line, which for the persona plugin is Character: and the roster's name — so a session is presented by the theme whose plugin started it, and no theme parses a card's prose. The avatar is the character the session started as: one switched to inside it with the plugin's use is not followed.
• Nothing waits forever. The page reconnects with a backoff capped at thirty seconds for as long as it is open. A permission prompt waits on a person, as the terminal's does, but an interrupt settles it as a deny, and so does closing its session.

What the terminal shows and does, and where the console carries each part, is terminal parity.

The pages of this feature

Key files

Notes

• The Genshin theme's palette, voice, scene and reactions, the views (the collector harbour), the terminal-mirror driver and the extension tiers are still proposals. The default theme is the world every one of them is measured against.
• Cost is what the SDK reports for the session's query since the host opened it. A session resumed in a new host process starts that count again, as a new terminal process does.