Agent Device Cloud
Sign in

Examples

What you can ask, and what to grant

Each example lists a request you can give your agent and the smallest access that makes it work.

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.

How cloud-agent tasks reach real devices

A cloud personal agent uses your home computer

“Check the logs on my home computer and explain why the app stopped.”

Grant Read access to the log folder on that Node, through an ADC integration supported by the agent. This is a file-inspection workflow; command execution needs separate authorization.

Fix failing tests in a repository

“Run the tests in ~/work/api and fix what fails.”

Grant Read & write on the repository folder, then also tick test.run. Choose Before changes or execution approval while you evaluate the agent.

On the device
adc-node roots list
adc-node templates add test --root ROOT_ID --command "npm test"

Search logs on a home server

“Find yesterday's 500 errors in the app logs and summarize the causes.”

Grant Read only on the log folder.

On the device
adc-node roots add /var/log/myapp --label Logs --read-only

Use an MCP server that lives on your laptop

“List my open pull requests with GitHub on my laptop.”

Grant Select the GitHub provider tools in Agent access. The GitHub token stays in the device's local file.

On the device
adc-node mcp add github --name GitHub --stdio npx \
  --args '["-y","@modelcontextprotocol/server-github"]' \
  --env-file ~/.config/adc/github-mcp-env.json

Operate an Android phone (in testing)

“Take a screenshot of my phone, then open Settings.”

Grant screen.capture, ui.inspect, screen.control, app.open and ui.action. Enable Accessibility, screen actions and notifications in ADC first. Add screen.control explicitly to existing grants and refresh the MCP tool list. Native ADC plugins need version 0.1.5 or later to forward intent and controlSessionId. Begin control, pass its token on actions, then end it; reads do not acquire control.

Work across several machines

“Compare the nginx config on my Mac with the one on the build server.”

Grant Read only on both devices. The agent sees each device as a target and names it in every call.

Let a teammate's agent use your device

“Read the design notes in the shared Research folder.”

Grant Share the device with your team or a named account, then each person authorizes their own agent.

ADC is not remote desktop, a hosted shell or public compute. Agents act only through tools you authorize, on devices you own or were explicitly shared.