yaohuangguan/remote-arc

**Controlled remote computer access for AI — across the computers you already own.**
Remote Arc connects ChatGPT, Claude, Codex, Cursor, and compatible MCP clients to Windows, macOS, and Linux computers you explicitly pair — without exposing a public port or requiring a VPN. It focuses on permissioned file, process, terminal, and explicitly shared browser access. Deterministic background tasks can persist independently of a chat; continuous AI reasoning is not currently claimed as a production capability.
Website · Dashboard · Remote MCP · Security
Source available for transparency and security review under a proprietary license. Not open-source licensed.
Chat → Remote Arc → your computer. Animated preview from the interactive demo in PR #101 (example data, no real device commands). Click to explore the workflow.
Why Remote Arc
- **Durable deterministic tasks** — approved commands, schedules, and condition watches can continue beyond one chat turn and be inspected later; new AI judgment still requires an active reasoning host.
- **Read-only by default** — newly paired devices start with safe inspection capabilities.
- **Per-device skill controls** — independently enable file edits, terminal execution, process controls, and recovery.
- **Outbound-only connectivity** — no public IP, VPN, router port forwarding, or inbound listener on your computer.
- **Local safety boundaries** — Trusted Write Locations, boundary approvals, protected sensitive paths, local undo, and a terminal Safety Guard.
- **Open MCP interoperability** — one OAuth-protected Remote MCP endpoint for supported AI clients.
- **Native execution core** — Remote Arc owns its filesystem, process, and terminal execution path rather than proxying another computer-control MCP server.
Quick start
Connect a Windows, macOS, or Linux computer:
The default device Agent and Execution Core are native Go. npm installs and
launches the checksum-verified binary; standalone and Homebrew installations
need no Node.js. --go remains a compatible alias and --ts selects the retained
TS runtime. Stop the active Agent before switching versions or runtimes.
Native downloads and Homebrew
Standalone 0.6.1 needs no Node.js or Go compiler. Installation and upgrade guide.
| Platform | Download |
| --- | --- |
| macOS Apple Silicon | remotelink |
| macOS Intel | remotelink |
| Windows x64 | remotelink |
| Windows ARM64 | remotelink |
| Linux x64 | remotelink |
| Linux ARM64 | remotelink |
SHA256SUMS · Release notes
The existing remotelink-go formula remains available for upgrades; install one formula at a time.
Then connect your MCP client to:
The browser pairing flow binds that computer to your Remote Arc account. From there, your AI client can only use capabilities currently allowed for that specific device.
User flow
Architecture
The hosted relay authenticates and routes requests. OS-level operations execute on the paired device, subject to the device's saved tool policy and local safety controls.
Monorepo
The Go Agent and Execution Core compile into one executable; extracting the core
does not introduce an IPC boundary. The core can be built/tested independently
with Go. Both engines preserve tool contracts, pairing, file/Undo formats and a
single execution lease. The cloud Relay and Dashboard remain TypeScript.
Native execution core
Remote Arc implements its local computer capabilities directly with Go and OS
APIs. The retained TS implementation is used only when --ts is selected.
Current native tools:
The primary core uses Go's os, filepath, os/exec, context and native
platform APIs. It owns bounded process output, cancellation, atomic replacement,
local Undo evidence, conflict fences and path policy. The Agent adds authenticated
outbound sessions, device configuration, checkpoints and local execution journals.
Atomic replacement and explicit durable synchronization are separate policies.
TS retains its atomic default; Go retains its durable default. This release does
not claim complete hardware power-loss protection. See the
persistence validation and
system architecture for boundaries and evidence.
Permission model
New devices start with the Safe preset.
Safe
Read-only local capabilities:
The native core also has internal dashboard capabilities such as
list_undo_actions and browse_directories. They let the authenticated