Remote ArcREMOTE ARC
Remote Arc: AI computer access, browser automation and device fleet
Remote Arc (RemoteArc) connects ChatGPT, Claude, Codex, Cursor and compatible MCP clients to authorized apps and Windows, macOS and Linux computers. Its browser tools support approved web workflows; its fleet scheduler can dispatch eligible work to an available device without requiring manual selection. Each device has its own permissions, and Arc adds bounded hosted conversations and scheduled reasoning over the same execution infrastructure.
Use the computer where the work already lives
Your repositories, files, runtimes, credentials and command-line tools can stay on your own machine. Remote Arc exposes named MCP capabilities for inspecting directories, reading files, making supported edits, checking processes and running approved commands. The AI asks for a specific tool operation and the paired device executes it locally, so you do not need to move an entire development environment into a hosted VM just to let an AI help with real work.
Separate AI authorization from device permission
OAuth authorizes the AI client to your Remote Arc account, while each paired computer keeps its own policy. A development workstation can allow file edits and managed terminal commands while another machine remains read-only. Trusted Write Locations, protected paths, per-tool permissions and explicit approvals let you narrow ordinary file workflows without pretending that powerful terminal access is risk free.
No inbound Remote Arc port
The local agent establishes an outbound connection to the hosted control plane. Normal setup does not require port forwarding, a public IP address, a VPN into the machine or a publicly reachable local MCP server. The hosted side handles identity, discovery and routing; operating-system execution still terminates on the paired computer under the local user account.
Keep the AI client replaceable
Remote Arc uses MCP as the product boundary exposed to compatible AI clients. That means the client can change without rebuilding the device connection model. You can connect ChatGPT, Claude, Cursor or another supported MCP client to the same account while keeping paired computers, device policy and revocation controls independent from the conversation interface.
Connect supported apps through one account
Connect Apps and computer devices under the same Remote Arc account, then use the operations actually supported by each integration. Authorization and tool availability depend on the selected app and provider; the catalog does not claim every action is supported.
Support short actions and durable work
For immediate work, an AI can inspect state and call device tools during the conversation. Connect can persist supported deterministic commands, schedules and condition watches. Arc adds bounded hosted reasoning, conversations, reusable Skills and Tasks with fresh judgment when scheduled. Each run records actual observations and results; missing permissions, dependencies and uncertain effects remain explicit blockers.