terminal-io

The live terminal pane and the channels that feed and sustain it — embedding the tmux pane in the browser, the command line living outside xterm, files dropped into the prompt, and the socket that reopens itself after a drop.

Inside the session-console the live session is a real terminal, and one cluster of concerns answers a single question — how does a human read and drive that terminal pane? These are the live-terminal half of the console; its sibling surfaces (session-activity, session-rename, session-reorder, session-graph) are the other half — which session you are on and how it is labelled and ordered, not how you drive it.

• session-peek — embedding the tmux pane in the browser (capture-pane / send-keys, xterm.js), the dormant original the console's live terminal grew from.
• term-input — the contract that the command line lives outside xterm: a read-only display, a separate input that owns the keys.
• file-attach — a file dropped, pasted, or picked on the prompt rides to the worker's /tmp, the prompt left holding its path.
• reconnect — the terminal's socket reopens itself after a real backend drop, with visible backoff, so a pane never needs a manual refresh.

This node owns no source of its own — each child keeps its files, [links](/reference/spec-forge/links/), and drift. It exists so the console's terminal cluster reads as one surface, not a flat fan-out beside the session-row surfaces.