Module attach 

A4: the TUI over SocketTransport (synaps --attach). synaps --attach [ID] [--observe|--takeover] [--keep-warm] [--no-confirm-answers] — the TUI over SocketTransport (PLAN-phase3 A4). Client diet: no EngineHost, no Runtime, no ExtensionManager, no MCP, no skills index — config, builtin commands, keybinds, the render thread and the event stream only. Plugin commands / interactive plugin commands are not available over the socket yet (Query{Commands} is phase 4).

Structs

AttachOpts

What to attach to.

LiveSession

The slice of Welcome.sessions the attach decision needs.

Functions

adopt_banner

One-line inventory of the daemon’s other sessions, shown when a plain synaps adopts the daemon (F1): the lid-close user must be able to see their parked task, without being surprise-attached to it. None when nothing else is there. Rows read like /sessions rows (same label, same state clock — state_since, not created_at — and ~ paths), and the line points there.

attach_mode

SYNAPS_ATTACH_MODE=mirror|observe|takeover default, overridden by flags.

choose_attach

What to send: Existing for an explicit or sole live session, Create for --new, --continue, or no live sessions. Errors are user-facing. notice is a one-line stderr message when a live session was picked implicitly (no id given).

daemon_not_running_message

What --attach prints when there is no daemon to attach to: says so, and how to start one (profile-aware). The SYNAPS_DAEMON_AUTOSPAWN hint only appears when autospawn really is off; otherwise the daemon was there a moment ago (idle shutdown, crash) and re-running starts a new one.

run_attached