Control agent spending from one inspectable boundary.

Create a control in the browser, then run the version-pinned CLI command in the agent workspace. You do not need to clone a repository, install a global binary, or save an executable file.

npx allowanceos@0.1.0 connect AOS-XXXXX-XXXXX --server https://qa.fatbeef.tech/allowanceOS

npx fetches the exact package version into npm's cache and runs it. The temporary pairing code expires after ten minutes and works once.

A control assigns a budget, a per-payment cap, recipient names or addresses, an expiry, and a pause state to one agent connection.

Use the product

1. 1

   Open onboarding or choose Create control from the product.

2. 2

   Name the control and set the total budget and per-payment limit.

3. 3

   Add one recipient per line and choose an expiry in the future.

Control management stays in the authenticated product in this release. The future operator CLI will use a browser-approved device flow instead of permanent management keys pasted into a shell.

Run the generated npx command in the intended agent workspace. npm fetches and executes the exact package version; no repository, global install, or manually managed script is involved.

npm view allowanceos@0.1.0 dist.integrity

npx allowanceos@0.1.0 connect AOS-XXXXX-XXXXX --server https://qa.fatbeef.tech/allowanceOS

Pairing writes .allowanceos.json with the server, control ID, connection token, and locally generated EVM and Solana session keys. AllowanceOS sends only the public addresses to the server. It also writes ALLOWANCEOS_AGENT.md with the authorization instruction for the agent.

Generate another pairing code

Open the control inspector and choose New code. Management actions require an authenticated operator session.

Redeeming a new pairing code rotates the connection token. A workspace connected with the old token will stop authorizing attempts for that control.

The same ownership model applies to both chains. You approve a token deposit from your wallet. The paired workspace receives a separate session key with limited authority. AllowanceOS never asks for your wallet seed phrase or private key.

The agent must ask the CLI for a decision before it calls the payment tool.

npx allowanceos@0.1.0 authorize --amount 1.25 --recipient research-api --description "Buy a research result"

{
  "decision": "allowed",
  "code": "ALLOWED",
  "explanation": "This attempt fits the active control.",
  "attemptId": "att_..."
}

{
  "decision": "denied",
  "code": "PER_PAYMENT_LIMIT_EXCEEDED",
  "explanation": "The amount exceeds the per-payment limit.",
  "attemptId": "att_..."
}

Continue to the payment tool after an allowed decision and exit code 0. A denied attempt still appears in Activity with its reason code.

The Activity page reads attempts reported through one connection. Allowed attempts add to observed spend. Denied attempts remain in the ledger but do not consume the budget.

npx allowanceos@0.1.0 status

npx allowanceos@0.1.0 activity

Pass --control <id> and --server <url> to inspect another control without changing the workspace configuration.

Authenticated operators can pause, resume, inspect, and reconnect controls from the product. Connected workspaces can read only their own control and activity using their scoped connection token.