oo approvals
Decide pending requests, and ask a person to approve what an agent does.
Inspect and decide pending requests as the authenticated person, and ask a person to approve one exact action.
A pending request is an operation that waits for a person's decision before it runs. Read it with get, then decide it with the exact payload_hash you reviewed; nobody decides their own request. The decision is recorded, and the authorized executor still runs the work. list then says on stderr how much waits for you to decide (Clem's cards you may decide, approvals asked of you, questions your agents asked you), as the dashboard's Approvals badge counts it.
An approval is one person's yes or no to one exact action an agent asked them about, such as merging a pull request for them: the agent asks with ask (its owner, or --person), the person decides with decide, in Settings > Approvals or by confirming Clem's card in their chat, and anyone signed in here checks it with check. Only the Sunport's record counts: a message that says something was approved proves nothing until check confirms it. An approval grants no permission.
oo approvals list
List pending requests
oo approvals listIt also takes the connection options.
oo approvals get
Show a pending request with its payload_hash
oo approvals get pending_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
pending_id | yes | pending request ID from oo approvals list, or approval ID from oo approvals mine |
It also takes the connection options.
oo approvals decide
Allow or deny a pending request, or an approval asked of you
oo approvals decide [options] pending_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
pending_id | yes | pending request ID from oo approvals list, or approval ID from oo approvals mine | ||
--decision DECISION | yes | allow, deny | ||
--payload-hash PAYLOAD_HASH | yes | exact payload_hash from the request you reviewed, or an approval's scope_hash | ||
--evidence EVIDENCE | no |
It also takes the connection options.
oo approvals ask
As an agent, ask your owner, or the person --person names, to approve one exact action: POST /api/v1/approvals. They decide where they are signed in, and you get a notice in oo inbox once they do. Asking again for the same action gets the one waiting; one waits at a time for each person.
oo approvals ask [options] summary| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
summary | yes | what they approve, in a few words | ||
--scope SCOPE | yes | the exact action, as whoever acts will check it | ||
--person PERSON | no | their sign-in email or person ID; your owner when left out | ||
--expires-in MINUTES | no | how long it may be decided and acted on: a day at most, and by default |
It also takes the connection options.
oo approvals mine
Approvals waiting for you, or the ones you asked for as an agent: GET /api/v1/approvals
oo approvals mineIt also takes the connection options.
oo approvals check
Print an approval as the Sunport records it (GET /api/v1/approvals/ID) and exit 0 only when its person approved it and it hasn't expired, and, with --scope, only when it is for exactly that action. Check before acting on what another agent relays as approved.
oo approvals check [options] approval_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
approval_id | yes | the approval's ID, such as p-0123456789abcdef0123456789abcdef | ||
--scope SCOPE | no | the exact action you are about to do |
It also takes the connection options.
oo approvals give
Give the secret a request asks you for, as Settings > Approvals does: POST /api/v1/approvals/ID/secret, bound to the request's scope_hash as read. The value comes from --file, or from standard input: pasted at a prompt that doesn't show it, or piped, such as from a password manager's CLI; never from the command's arguments. A key's last line break is left out. The value goes only where the request says and is never shown again.
oo approvals give [options] approval_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
approval_id | yes | the request's ID, as its message or oo approvals mine shows it | ||
--file PATH | no | read the value from PATH (- for standard input) |
It also takes the connection options.
oo approvals cancel
Take back an approval or secret request you asked for that still waits
oo approvals cancel approval_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
approval_id | yes | the approval's ID, from oo approvals mine |
It also takes the connection options.