Phone control
Away from your desk? Keep working from your phone.
Your phone is a terminal control, not just a notification screen. Pair a browser, switch between existing terminals, send instructions and respond to the CLI while the work runs on your computer.
- 01Computer · runs the work
- 02Paired browser · live terminal
- 03You · type, send, respond
Before you start
- Keep the host computer and Termdock running and reachable.
- Use a phone browser on the same trusted network for initial setup.
- For access away from the LAN, configure a network route such as Tailscale or ZeroTier.
Open browser access on the desktop
In Peer Sessions, enable the host and browser access. Scan the displayed QR code or open its URL on your phone.
Pair once
Choose Pair and compare the codes on the computer and phone. Confirm the pairing on both sides. The browser remembers its device key for this address.
Do more than watch
Choose an existing terminal and use the touch input bar to type and send a command or instruction. Use the terminal selector to switch tasks, and Esc or Ctrl+C when appropriate. A paired LAN browser can type without asking for control of each terminal again.
Reconnect when you return
Reloading the browser returns to its previous terminal when it is still available. Closing the browser view does not end the host terminal. Revoke a lost device from Peer Sessions.
Know the limits
- The browser is not the complete desktop app: creating terminals, editing files, Git writes and the desktop Workstream panel are separate capabilities.
- Typing into an interactive terminal can change files or stop work. Inspect the prompt before sending a command, and do not resend blindly after an uncertain connection.
- The built-in LAN entry uses HTTP and is intended for trusted networks. Pairing is not a substitute for a trusted network path; Termdock does not set up a public relay for you.
What you should end up with
You can actually operate a running terminal from your phone, instead of waiting until you are back at the keyboard.