Mobile relay and remote access

Pair a computer#

Remote access connects the phone to a reachable desktop installation. Start from the phone navigation drawer and select Remote, then choose Pair a computer. The desktop also exposes View → Settings → Mobile Gateway for pairing and gateway status. The connection is private to the paired desktop and phone; the desktop remains the authority for local projects, runtimes, files, terminals, and Git.

When no computer is paired, Remote shows No computers yet with the explanation Pair a computer to bring its projects and chats onto this phone. After pairing, the Remote library lists available computers, projects, and tasks. Host scope pills include All and the name of each computer. Projects view, Priority view, and Search remote chats help locate the right task.

How the mobile connection works#

The mobile relay is a paired connection to the desktop's Mobile Gateway over the configured private route. Requests go to the desktop, which checks the device's granted access before acting. Task updates and permitted views return to the phone. The repository, coding runtime, and vendor credentials remain on the computer.

flowchart TD
  accTitle: Mobile Remote connects to the desktop
  accDescr: The paired phone sends permitted requests over a private connection. The desktop checks permissions, runs local tools, and returns task updates and previews.
  A[Paired phone: Remote] -->|Messages and allowed requests| B[Private connection]
  B --> C[Desktop Mobile Gateway]
  C --> D[Device and task permission checks]
  D --> E[Local Code runtime and project]
  E -->|Task updates and permitted previews| A

Account-backed mobile Chat uses a separate service path and does not depend on this connection. It is not a copy of a desktop Code task.

Open and supervise a task#

Select a project and task from Remote to open the desktop-backed transcript. The task top bar can return Back to Remote, open the paired browser, or open work surfaces. A task message can be sent from the phone when the remote task is reachable. The phone can also show Git, Agents, Files, and Usage in the Work surfaces sheet. File previews are read-only, while Git status and diffs provide evidence for desktop follow-up.

Reconnect after an interruption#

If the desktop sleeps or the private route is lost, the phone cannot perform desktop actions. Restore desktop availability and the route, then reconnect to the task to obtain its current state. A stale mobile view is not confirmation that an action completed. Check the restored transcript and approval status before repeating a request. Pairing can be revoked or its scopes changed in desktop Mobile Gateway settings.

Desktop and mobile permissions#

The desktop performs local Code work; the phone provides a paired control and observation surface. Stage, commit, push, runtime installation, and free project-terminal work remain desktop actions. Remote access does not create cloud synchronization for Code state and does not turn the phone into a hosted Code relay. Browser states such as Waking the desktop tab…, Reconnecting to the desktop…, and The desktop stream stopped. indicate the paired desktop connection.

Account-backed Chat, Scheduled Tasks, and Skills follow their own account or paired-host availability. Mobile covers the setup and recovery surface.