Prepare one bounded workspace

Start with one non-sensitive repository or test directory on a supported macOS, glibc Linux or Windows device. The installed Connector includes its runtime, but it needs permission to configure user-level startup and write to the current user's local application directories.

  • Use an HTTPS ADC deployment reachable by the device.
  • Begin with a selected folder, not full-device access.
  • Plan the first call as read-only.

Pair the Connector

Sign in to the console, select the target platform under Devices and run the generated command. The code is short-lived and one-time. Pairing creates a local Ed25519 identity and configures launchd, systemd --user or Windows Task Scheduler.

curl -fsSL https://devices.example.com/install.sh | sh -s -- \
  --url https://devices.example.com --code 'PAIRING_CODE'

adc-node status
adc-node roots list

Create the smallest useful Agent access

Choose the paired device, the single workspace folder and read tools such as file.list, file.read and file.search. Keep writes and execution disabled until the read path succeeds. The authorization is a revocable object; a CLI or MCP connection binds to it rather than copying account authority.

Verify execution and evidence

Connect the CLI to the authorization, inspect the device and read one known file. Success means more than a response: the device is online, the result is terminal and Activity records the matching policy decision and receipt.

adc login --url https://devices.example.com
adc connect first-agent --json
adc node list --json
adc invoke file.read --node node_example \
  --args '{"path":"/path/to/workspace/README.md"}' --json

Expand only after the read path works

Add file.patch or a local test template only when the workflow needs it. Use approval for writes or execution while evaluating a new Agent. If a request fails, preserve its error code and invocation identity instead of granting broad access as a first response.