Remote TUI operations

Use when: the agent process runs somewhere that isn’t your laptop (a K8s pod, a build worker, a shared session server) and you want to drive it interactively without giving up the operator UX. Or when one daemon needs to serve many concurrent sessions with different callers, each with their own permission scope.

What ships

• core-agent-tui — Bubble Tea client that speaks HTTP + SSE to any daemon that mounts the core-agent attach API.
• Multi-session daemon — one server process, many concurrent sessions, per-caller ACLs enforced at the transport layer.
• Transparent resume — if the daemon restarts, the client reconnects and replays from the last-seen seq.
• Mid-turn interrupt from anywhere — Esc in the TUI, /interrupt slash command, or POST /sessions/<sid>/interrupt from a script.

Tip

The client and the in-process TUI share their slash-command surface — /stats, /context, /compact, /done, /btw all work the same whether you’re local or attached.

Where the details live

• Attach mode TUI — the depth reference: transport, ACLs, resume protocol, deployment shapes.
• Multi-session daemon — daemon config, session isolation, per-caller scope.
• Sessions and event log — the durable log that resume replays from.