Agent Device Cloud
Connect your agent to the computers, servers and phones where the work happens.
Your agent plans the task. ADC connects it to the devices you authorize, routes tool calls and returns results. Use your agent from anywhere; run the work where your code, data and tools already are.
Run the tests in ~/work/api and fix whatever fails.
file.search~/work/api12 matchestest.run~/work/api2 failedfile.patchsrc/auth.tsApproved by youtest.run~/work/api48 passedFixed the expiry check in src/auth.ts. All 48 tests pass.
How it works
Three steps to your first task.
- 01
Install the connector
Run one command on macOS, Linux or Windows, or install the Android app. The console gives you the exact command.
curl -fsSL https://adc.220719.uk/install.sh | sh -s -- \ --url https://adc.220719.uk --code PAIRING_CODE - 02
Choose what to share
Pick the folders and tools an agent may use, and which actions need your approval.
~/work/api Read & write Approval Before changes or execution - 03
Connect your agent
Install the plugin or Skill, or add the MCP URL. Then ask in plain language.
npx skills@latest add https://adc.220719.uk \ --skill agent-device-cloud
Windows Node and Android Node are in testing. They are available to try, but compatibility and reliability are still being validated. An available installer does not mean every system, phone model or operation has been verified.
What agents can do
Ask in plain language. The work runs where your files already are.
More examplesHow a cloud agent reaches your devices- “Run the tests in my repo and fix what fails.”
file.search · test.run · file.patchMac or Linux workstation - “Find yesterday's 500 errors in the logs on my home server.”
file.search · file.readLinux server or NAS - “List my open pull requests with the GitHub MCP on my laptop.”
adc-node mcp add githubToken stays on the device - “Take a screenshot of my phone and open Settings.”
screen.capture · app.openAndroid Node · in testing
Works with your agent
Bring the agent you already use.
Plugins with guided setup are available for:
- Zion
- Claude Code
- Codex
- Cursor
- Copilot / VS Code
- Gemini CLI
- Factory Droid
- Pi
- Cline SDK / CLI
- OpenCode
Download the plugin for your agent, then send this first message. It walks you through sign-in, device and access.
Help me start using ADC, connect my device and configure access.Safe by default
Your device keeps the final say.
- You choose the folders
Agents see only the folders and tools you grant, on the devices you pick.
- No open ports
The connector only dials out. No inbound port, VPN or SSH key on the device.
- Approve before it acts
Require your approval for file changes, commands or every operation.
- Every action recorded
Activity shows which agent asked, what ran where, and the device's receipt.
Full device access is not a sandbox — it runs with your OS user's permissions. Start with one folder. Security model
FAQ
Common questions
Hosted or self-hosted?
Use the official hosted service at adc.zioon.tech, or run the same open-source application on your own server with Docker Compose. Both share the same permissions, approvals and device software.
Which devices are supported?
macOS 13.5+ and glibc Linux (arm64/x64) provide available desktop connectors. Windows 10/11 x64 and the manually installed Android Mobile Node are in testing.
Does ADC copy my files to the cloud?
No. It never crawls or mirrors your disk. Only the result of a call you authorized passes through the service, where it is recorded for audit.
How is this different from SSH or remote desktop?
Remote desktop is useful for visual assistance, and SSH is a mature way to run remote commands. ADC packages device discovery, tool calls, per-agent permissions, sharing and task records into one service for agents and applications. It can coexist with your existing remote access.
What happens when my laptop sleeps?
New calls report the device as offline. The connector reconnects on its own when the device wakes.
Start with one device and one folder.
Use the official hosted service, or self-host the same app.