Agent Device Cloud
Sign in

Architecture

One control plane. Execution remains local.

Use familiar Agent interfaces. ADC applies authorization and routing centrally; the selected device validates and executes each tool locally.

Current request pathAuthorized tool call
01
Agent interface

Use MCP, CLI, Skill or SDK to call authorized tools on the selected device.

MCP clientCLIOfficial SkillSDK
02
Control plane

Authenticates, authorizes, routes and records. It does not execute your tools.

IdentityAuthorizationPlacementAudit ledger
03
Device connector

Maintains an outbound wake connection, advertises built-in and local MCP tools, and renews active leases.

WebSocket wakeBuilt-in toolsLocal MCP ProvidersLease and ACK
04
Local runtime

Revalidates local policy, runs built-in tools or calls the selected MCP Provider, and persists a receipt.

Path validationLocal executionReceipt ledger
Control plane boundaryDevice boundary

Request lifecycle

  1. 01requested

    The client creates a typed invocation from its current Agent authorization.

  2. 02authorized

    The control plane resolves the device and evaluates every policy layer.

  3. 03approval?

    Approval-sensitive work waits without occupying a device lease.

  4. 04leased

    The device claims, acknowledges and renews a bounded execution lease.

  5. 05running

    The local runtime validates the resource again before executing.

  6. 06terminal

    The terminal result, receipt and optional artifact return to the control plane.

Effective authorization

An operation proceeds only when every independent boundary permits it; no layer can expand a narrower one.

Account boundarySame account owner
Agent grantDevice and tool selected
Device policyWrites and execution enabled
Exposed folder/Users/me/work
Live capabilityfile.patch advertised

Delivery semantics

queuedleasedrunningsucceeded

Dispatch is at-least-once. Side effects require an actor-scoped idempotency key and are recorded in a local durable ledger before execution.

If execution may have happened but no terminal receipt can be proven, the result is unknown_outcome and is never silently retried.

Data boundaries

Control plane records

Accounts, disclosed path metadata, grants, invocation state, requested results, artifacts and receipts.

Device retains

The private device key, unrequested files and the local environment. Only an authorized operation can return content.