Skip to content
quoxcli
Preview. This site is a preview of cli.quox.ai and is not indexed. Some pages describe work that is not released yet.

Say yes or no to a risky step

What you get: you decide, in the moment, whether an agent may restart a service, change a file or run a command on a server. Nothing risky runs until a person says yes.

Ask Quox

Section titled “Ask Quox”

Just ask, in your own words:

quox · talking to Quox

Is anything waiting for my approval right now?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 6ms

◐ INBOX │ pending ✔ INBOX │ pending │ 0 count, 0 items · 2.7s

⛓ AEE │ envelope opened · stream_success

All clear, nothing is sitting in the approval queue right now. Your inbox is empty.

If something comes in, you'll see an approval card appear in the terminal and the dashboard inbox. Anything else I can help with?

12.8s · 1 tool · 0 approvals

A real turn on our own install (quox 0.3.0, 13 Oct 2026), replayed at speed. Names changed. Type the same words into quox.

Quox read the approvals queue and said it was empty. When something is waiting, it lists it, and you answer on the card.

Do it yourself

Section titled “Do it yourself”

In the conversation

Section titled “In the conversation”

When an agent reaches a step that needs a human, a card appears with the action, its scope and its risk.

  • Press a to approve, d to deny, or o to open the card in the dashboard.
  • These keys only act when your draft is empty, or after you press Tab to focus the card, so a stray a in a sentence never approves anything.
  • Keys arm after 300 ms, nothing defaults to approve, and Enter never approves.

If you were busy, list what is waiting and answer by number:

/approvals
/approve 1
/deny 2

From any shell

Section titled “From any shell”

Approvals live on the server, not in your terminal, so you can answer them from anywhere: another machine, a script, or a phone over SSH.

quox inbox 
# how much is waiting for a human?quox inbox statsInbox Stats─────────────────────open                0in_progress         0waiting             0resolved            1pending_approvals   0awaiting_human      0# everything in your organisation waiting for a humanquox inbox list --awaiting-humanNo results.
From a real run on our own install, on a quiet afternoon with nothing waiting. Trimmed to the rows that matter here.

When something is waiting, read its full context first, then answer:

answering an approval 
# who asked, on whose behalf, and why it needs youquox inbox show <item-id># say yes, with a note that is kept with the decisionquox inbox respond <item-id> --action approve --comment "ok for web-01 only"# or say noquox inbox respond <item-id> --action reject --comment "not during the release"
Commands as quox inbox --help documents them at 0.3.0.

respond also takes an approval id handed to you by an agent, and --action defer or --action resolve.

What just happened

Section titled “What just happened”

The agent’s call was held on the server, not run. Your answer is stored on the item with who decided, when, and your comment. Approve, and the action runs and ends with a receipt line in the conversation. Deny, and nothing runs.

Check it yourself

Section titled “Check it yourself”

To see what an approved call actually did, ask for its stored result:

Terminal window
quox approvals result <approval-id>

In the conversation, /proof walks the evidence chain for the last tool call. To check a receipt against the witness chain yourself, see Check a receipt yourself.

Undo

Section titled “Undo”

A denial stands; the agent has to ask again. An approved action has already run, so it cannot be un-approved. Read the card’s scope before you press a.

Next

Section titled “Next”