Phone and Browser Access

Connect from your phone

• Open Peer Sessions on the desktop and enable the host.
• Enable browser access, then scan the QR code or open the displayed URL on your phone on the same network.
• Choose Pair. Compare the verification code on both devices and approve on both sides.
• Select a local workspace and terminal. A paired LAN browser can type without a separate approval for each terminal.

The QR code is generated locally and contains the URL, not a pairing secret. The desktop must remain running and reachable. Wi-Fi client isolation can prevent the connection.

Workspaces and screen

LAN browsers see all local workspaces and their existing terminals. The “workspaces available for remote mounting” list controls other Termdock devices, not this browser list. HOME and filesystem-root workspaces expose terminals only, not files.

On the first connection, you land on the desktop’s active local terminal when available. Later reloads and reconnects return to the browser’s last terminal if it still exists, with the desktop selection as fallback. Switching on the phone does not move the desktop view.

The browser uses the same workspace and terminal interface as the desktop. Narrow screens show one terminal at a time with previous/next controls and a terminal selector. Other terminals keep running on the desktop. Rotation or opening the keyboard does not resize the desktop PTY automatically.

Input and file boundaries

Use the touch input bar to compose text and send it. Enter/Send submits; Shift+Enter keeps a newline. Esc and Ctrl+C do not send an unfinished draft. If delivery is uncertain, check the desktop result before trying again. Input is not queued offline.

File browsing and text-file viewing are read-only and stay within the workspace root. File editing, saving, renaming, deletion, Git operations, desktop settings changes, creating/deleting terminals, and chaining through peer/SSH workspaces are not available in the browser.

Paired LAN browsers can type concurrently. This is separate from the single-writer takeover policy for terminals created by another Termdock device.

Remember and revoke devices

The browser stores a device key for this URL and reconnects without repeating pairing. In Peer Sessions, revoke one paired browser or remove all browsers; revoked devices disconnect and must pair again. Revoke a lost phone immediately.

Choose the network address and a fixed port in the desktop browser-access controls to keep the URL stable across restarts. A chosen port that is occupied reports an error rather than changing silently. Changing the URL’s IP or port requires pairing again. You can opt into automatic browser access on launch while the host is enabled.

Network safety and access away from home

The built-in LAN entry uses HTTP. Use it only on networks you trust: pairing does not protect the initial web page from an active network attacker. No domain or certificate setup is needed for this basic connection.

For access away from home, set up Tailscale, ZeroTier, or a similar network yourself, then select its offered address on the desktop. Termdock does not deploy a public relay for you. Full PWA installation requires trusted HTTPS; adding a home-screen shortcut does not provide offline terminal operation.