Devices
Pair a computer or server with your account and run it as a device your agents can run commands on, with standards device pair and standards device serve.
standards device turns the machine it runs on into one of your devices: a computer or server paired to your account, listed under Settings → Devices, that agents you grant it to can run shell commands on with exec_command. It is the worker the Devices settings tell you to install. A browser is paired from its extension instead: see Browser devices.
Before you pair
- macOS or Linux. Any other platform is refused before any request.
- A saved profile. The device credential is stored in the profile, so
devicecommands need one saved withstandards login. A key passed with--api-keyor read fromSTANDARDS_API_KEYalone is refused withDevice pairing requires a named Standards profile. See How to use the CLI.
npm i -g @standards/cli
standards login --url https://api.standards.new/v1 --name prodCommands
| Command | What it does | What it prints |
|---|---|---|
standards device pair --name "<name>" | Pairs this machine with your account under that name. --name is required. | Paired <name> (<deviceId>). |
standards device serve | Runs the device worker in the foreground: it waits for commands and runs them. | One line per command it starts and ends. |
standards device status | Shows the paired device. | Its id, name, platform, architecture, hostname and status (online, offline or revoked). |
standards device revoke | Revokes the device's credential and forgets it on this machine. | Nothing. |
status, serve and revoke act on the device paired with the current profile; without one they stop with No paired device; run standards device pair first.
Pair
standards device pair --name "Build server"device pair registers this machine — its platform, architecture and hostname — and stores the device credential it receives in the profile, in ~/.standards/config.json. The device is yours: only you see it, and only your own private agents can be granted it.
Serve
standards device serveConnected as Build server
Waiting for commands — press Ctrl+C to disconnect
Running <commandId>: <intent>
Completed <commandId> with exit code 0The device is online while device serve runs and offline once it stops. Keep it running — in a terminal, or under your service manager — for as long as agents should reach the machine. Ctrl+C disconnects it. serve refuses to start on a device that was revoked, or from a machine whose platform does not match the paired one.
Commands run as you
The worker runs each command with the operating-system account that started device serve, on that machine. Run it under an account that can touch only what agents should.
Allow agents
A paired machine gives agents nothing until you allow it. In Settings → Devices, switch on Allow agents on its row. From then on, an agent you granted the device to (device:<deviceId>) gets exec_command on it whenever it works for you — in your conversations, or a run you start — while the device is online. Switching it off takes the tool away again.
A device needs you at the keyboard: a routine cannot hold one, and a run a trigger fires, with nobody behind it, gets no command tool on it.
Revoke
standards device revokedevice revoke revokes the credential, which cancels the commands still running, and removes it from the profile. Removing the device from Settings → Devices does the same from the app. Pair again to bring the machine back.
Next steps
- Browser devices: pair a browser and the tools an agent drives it with.
- Agents and routines: grant a device to an agent.
- How to use the CLI: profiles, global flags and exit codes.
- Book a demo