Remote ArcREMOTE ARC
Remote Arc security and trust model
Remote Arc separates AI-client authorization, hosted routing and local operating-system execution so each paired computer can keep its own explicit capability boundary.
Outbound device connection
The local agent connects outward to the hosted relay rather than requiring a normal inbound Remote Arc port. A computer therefore does not need port forwarding or a publicly reachable listener for ordinary Remote Arc use. The hosted control plane can route authenticated tool calls to an online device through that existing outbound connection.
Separate client authorization from device identity
AI clients authorize with OAuth while paired computers receive independent revocable device identities. This avoids one shared master credential for every client and machine. Revoking an AI grant does not require re-pairing every computer, and removing one computer does not force all AI clients to authorize again.
Per-device capability policy
Read, edit, terminal, browser and long-running task capabilities can be controlled separately. File-oriented work can be narrowed with Trusted Write Locations, workspace boundaries, protected sensitive paths and approval steps. The policy is attached to the device rather than hidden inside a prompt, so a different AI client sees the same local boundary.
Terminal access is intentionally more powerful
When terminal execution is enabled, commands run with the permissions of the local operating-system user. Remote Arc does not claim that workspace settings sandbox an unrestricted shell. Users should enable terminal access only on devices where that authority is appropriate and prefer narrower file tools when they are sufficient.
Local recovery without hosted filesystem backups
Supported write_file and edit_block operations can create Local Undo snapshots on the paired computer. A restore checks the post-edit revision before overwriting newer work. Snapshot contents remain local; hosted Remote Arc keeps the operational metadata required for identity, routing, policy, task state and audit rather than storing a backup copy of the whole device.