Module remote 

Remote terminals: the connection a terminal pane belongs to, and its status.

docs/specs/SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md. This is P0, the groundwork: the connection model (§4) and the status registry the frontend’s existing connection UI reads (ConnStatusOverlay, the connection typeahead, conn-status.ts). WSL terminals (P1) and SSH terminals (P2) build on it; nothing here spawns a remote shell yet.

Re-exports

pub use conn::ConnTarget;

Modules

address

Which machine a remote pane is connected to, by name and address, for its stats badge tooltip (blockstats.detail).

agent_access

Which agents the user has let use which SSH hosts (spec §8.2 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md).

askpass

The SSH askpass bridge (spec §5.3 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md).

conn

A pane’s connection, parsed from its connection block meta.

files

Files on an SSH host, through AgentMux’s helper (spec §6.3 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md): one ssh -T host -- agentmux-remote serve --stdio per connection, kept open while it is used and closed after IDLE_CLOSE without a call, speaking agentmux_remote::fsproto. Requests carry ids, so any number can be in flight on one connection.

helper_consent

Asking before AgentMux’s helper is installed on a host (SPEC_REMOTES_PANE_2026_10_05.md §4.9).

helper_hosts

The SSH hosts AgentMux’s helper has answered on (spec §7.1 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md): on such a host a new terminal pane is durable unless the pane, the connection’s settings or the global setting say otherwise. Kept in remote-helper-hosts.json under AgentMux’s config dir; a host is its canonical connection name (ConnTarget::name), so one host is one entry however it is spelled.

helper_install

Installing AgentMux’s helper (agentmux-remote) on an SSH host, for durable sessions (spec §6.2 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md).

host

One SSH host reached for commands rather than a terminal: a durable pane’s attach, the helper install’s scripts, and listing or ending the host’s durable sessions (SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md §6.2, §7.6). The one place these run ssh.

link

Whether an SSH connection is up, as its Remotes row and the overlay on its panes show it (status), kept true to the connection itself.

remotes

The Connectors → Remotes list (SPEC_REMOTES_PANE_2026_10_05.md §4.6): every remote machine AgentMux knows about, one record each, built from what srv already keeps:

sessions

The durable sessions on an SSH host (spec §7.6): what the helper’s daemon holds there, which pane (if any) each belongs to, and ending one. Behind Connectors → Remotes’ “Sessions…”.

ssh

SSH terminals (P2 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md).

ssh_config

The hosts the user’s ~/.ssh/config names, for the connection picker (P2 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md).

ssh_config_edit

Adding a host to the user’s ~/.ssh/config from Remotes, and finding a host’s Host line there (SPEC_REMOTES_PANE_2026_10_05.md §4.4).

status

Each connection’s status, published as connchange events.

wsl

WSL terminals (P1 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md).

wsl_fs

WSL folders in Hangar and the editor, through Windows’ own share for a distro’s files, \\wsl.localhost\<distro>\... (P1 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md).