REMOTE ARC

Troubleshooting

Resolve device, browser, authorization and availability problems.

Start with a paired device

Install the remotelink agent on Windows, macOS or Linux, sign in to the Remote Arc account that should own the device and approve pairing. Pairing creates a revocable device identity. The local agent then keeps an outbound connection to the hosted control plane so the computer can receive only the Remote Arc calls routed to that device.

Connect an AI client through Remote MCP

Compatible clients connect to the Remote Arc MCP endpoint over OAuth. OAuth authorizes the client to an account; it does not automatically grant every operating-system capability. Device discovery, tool descriptions and authorization are exposed through the MCP layer, while actual file and process operations terminate on the selected paired machine.

Choose the capability boundary per computer

Read access, supported writes, process inspection, terminal execution, browser interaction and task capabilities are separate controls. Trusted Write Locations and sensitive-path rules narrow supported file operations. When unrestricted terminal execution is enabled, the command still inherits the permissions of the local operating-system user, so it should be enabled only on devices where that authority is acceptable.

Use durable work for deterministic continuation

Long Tasks, schedules and condition watches can save work that should continue after the current chat stream ends. These mechanisms are best for bounded commands and checks with observable results. When the next step requires new judgment rather than a predetermined command, a supported reasoning controller must resume and decide what to do next.