What you will have
A paired computer that you can inspect remotely, with explicit control for terminal input and clear feedback when the connection is unavailable.
Step by step
Prepare the account service
Deploy the Go account service at an address your devices can reach. Use HTTPS and set AGENT_DOCK_ORIGIN to the public origin for a public deployment. The website and account service share the domain, while CLI execution remains on your computer.
Pair and enable remote management
In the desktop app, open Accounts & devices, enter the service address, and pair your computer with your account. Explicitly enable remote management. Keep the computer running and connected while you need access to its sessions.
Open the workspace on your phone
Open /app at the service address in a phone browser, or use the mobile client when an installer is available. Sign in with the same account, select the computer, and inspect the project and real terminal output before choosing an action.
Acquire control before entering input
Acquire the terminal control lease when a session needs a response. Check that you are targeting the intended session and running process. For team sessions, the operator controls output sharing and control permission. After a disconnection, reconnect and inspect the latest state before sending new input.
Check before you continue
- Keep the host computer awake, online, and remote management enabled.
- Check the target computer, session, and current output before input.
- Release control when finished and inspect state after reconnecting.
Questions about this workflow
Will my CLI keep running if the host computer is off?
No. The native CLI process runs on the host computer. A phone or browser is a remote interface, so the host must remain running and reachable.
Will input typed while offline be sent later?
No. Offline input is not automatically replayed. After reconnecting, inspect the current process and session state, reacquire control if needed, then explicitly enter the intended input.