Agent Device Cloud
Sign in

Get started

Connect your first device

Go from account creation to a first tool call without weakening the device's local boundary.

Before you begin

The hosted preview requires an account and a supported macOS, glibc Linux or Windows device. Installed connectors include their own Node.js runtime; Node.js 22 is only required for source development.

  • A reachable HTTPS ADC deployment.
  • A macOS 13.5+ or glibc 2.28+ Linux device on arm64/x64, or Windows 10/11 on x64.
  • Permission to run user-level startup and write to the current user's local application directories.
  1. 01

    Create an account

    Open the console and use one of the sign-in methods enabled by this deployment.

  2. 02

    Pair a device

    Open Devices, select the target platform, create a pairing code, and run the generated command.

  3. 03

    Authorize an agent

    Choose devices, folders, tools and an approval policy. Projects are optional.

  4. 04

    Connect a client

    Use OAuth MCP when available, or run adc connect after signing in to the CLI.

  5. 05

    Verify access

    Start with device.list or file.list, then inspect Activity for the policy decision and receipt.

Verify the complete path

After pairing, use the management CLI to create one narrow authorization and connect it locally. Replace the example device and path with values returned by your deployment.

Terminal
adc login --url https://devices.example.com
adc device list --json
adc access create \
  --name first-agent \
  --devices "Work Mac" \
  --folders all \
  --capabilities read \
  --approval never \
  --json
adc connect first-agent --json
adc invoke device.status --node node_example --args '{}' --json

What success looks like

  • The device is active and online in Devices.
  • Agent access lists only the intended device, folders and tools.
  • The invocation reaches a terminal result and Activity contains its policy decision and receipt.

Start read-only. Add write or execution only after the read path works and the approval policy is understood.