Crate agentmux_remote 

What srv shares with the helper: the frame protocol a durable session speaks end to end, the ring its history is kept in, and the file protocol of serve --stdio (which also answers Tower’s process frames, procs).

Modules

frame

The wire protocol between srv and a durable session (spec §7.2), carried end to end over ssh -T host -- agentmux-remote attach ...: attach only relays bytes between its stdio and the daemon’s socket, so these frames go straight from the daemon to srv and back.

fsproto

The file protocol between srv and agentmux-remote serve --stdio (SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md §6.1, §6.3), carried over one ssh -T host -- agentmux-remote serve --stdio per connection. Shared by both ends, so they can never disagree on it.

procs

The host’s processes for Tower (fsproto::Request::Procs, SPEC_TOWER_TASK_MANAGER_PANE_2026_10_08.md §8): sampled here, on the host, with the same readers srv uses locally (agentmux_procstats), so only a small frame crosses the link.

ring

A session’s output history: the last capacity bytes of everything its terminal wrote, addressed by offset in the whole stream (spec §7.2). A reattach asks for “everything after offset N” and gets it, or, when N has fallen out, everything still held plus how much was lost.

serve

agentmux-remote serve --stdio: file operations for srv over this process’s stdin and stdout (fsproto), one request at a time, until stdin closes (spec §6.1, §6.3). Paths are the host’s own; ~ and a relative path are under the user’s home. Nothing here opens a socket or reaches beyond what this user can already read and write.