Remote Workspaces

LAN pairing and mounting

• Run Termdock on both machines on the same network. Enable sharing on the host and choose the workspaces to share.
• Select the discovered device, compare pairing codes, and approve the pairing. mDNS discovers devices on the LAN.
• Mount a shared workspace from the workspace picker, then open a terminal in it.

Introduced in 1.18. Paired connections use end-to-end encryption without a cloud intermediary. Mounts persist across restarts and show offline states. Reconnects after sleep or network changes can reattach the original session. Sharing is opt-in and unsafe roots are rejected.

From 1.19, the Windows installer configures the LAN firewall path. If a network policy still blocks discovery or connection, check that policy rather than disabling security checks.

SSH workspaces Beta

From the workspace picker, add an SSH connection, enter the server address, authenticate, and choose a remote directory. Open terminals and switch tabs in the mounted workspace. Short connection drops reconnect automatically. SSH is a separate connection path from LAN pairing and remains Beta.

In 1.22, mounted remote workspaces expose file viewing and Git status as read-only. Do not expect local file editing or Git writes on these mounts. Custom SSH tab names are retained across app restarts.

Host inspection, takeover, and handback

Open Peer Sessions from the host’s bottom toolbar to inspect incoming terminal sessions. You can watch a session read-only or terminate it without terminating the other sessions.

For a terminal started by another Termdock device, the host can take over input and later hand it back. Only one side can type at a time. While the remote peer holds it, local Terminal API writes fail with SESSION_HELD_BY_PEER instead of competing for input.

When the remote device disconnects, its terminals remain running according to the host’s retention setting and can be reattached later. In Peer Sessions, choose bounded retention or retention until termination. This does not promise survival after the host or PTY itself stops.

How this differs from phone access

A browser connects to existing local terminals on the desktop and does not mount peer/SSH workspaces or create terminals. A desktop Termdock peer mounts explicitly shared workspaces. Configure each access path separately.