Agent tokens

A token lets an agent act for you, never with more than your role.

Most agents sign in through the browser and need no token (see Connect your agent). Use a token for CI, remote machines and agents that cannot open a browser.

  • One token per device or agent, with a label such as ci or cursor-work. Tokens start with sst_.
  • Shown once, when it is created. SDD Vault keeps only a hash of it.
  • Read-only tokens act as a reader in every project; read-write tokens act with your role. Neither can do more than you can, and the constitution stays owner-only.
  • A token covers the whole organization or the projects you choose.
  • Tokens expire: the lifetime is required, and the organization can set a maximum (sddvault org security set <ORG> --token-max-days <DAYS>).
  • They can be revoked at any time; agents using them are disconnected on their next call.

Create one

In the app, open Agent tokens. Or use the CLI:

Terminal
sddvault tokens create acme --label ci --days 30 --read-only --project payments

sddvault tokens list lists your tokens and sddvault tokens revoke <ID> revokes one. The app shows when, from where and with which client each token was last used.

Use it

Send it as Authorization: Bearer sst_…, or keep it in the SDD_VAULT_TOKEN environment variable and reference it from your MCP configuration.

Terminal
export SDD_VAULT_TOKEN=sst_...

sddvault init --token writes a token into the setup of agents that cannot sign in through the browser; add --read to make it read-only.

Terminal
sddvault init acme/payments --token --read