oz0 approval answer
For: Operators and developers looking up a command.
Answer a question an agent asked with oz.ask_user. The agent reads the answer and goes on. When the question offers choices (approval list shows them in brackets), the answer must be one of them. When it asks typed fields (approval list shows them as {name: kind}), the answer is one JSON object of their values, such as '{"day": "2026-10-12", "count": 2}', which the job checks against the fields.
To decline, use approval deny with a comment; the agent is told who declined and why.
Only a pending question takes an answer: an answer to any other approval is refused, so this command never approves a tool call. Answering needs the content permission on the tenant, since the question is the job's content; without it the answer is refused (permission denied), and approval deny still declines.
Usage
oz0 approval answer JOB APPROVAL ANSWER [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--comment | string | a note for the job's history | |
--tenant | string | default | tenant |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.