oz0 eval samples
An agent without an outcome check may have a share of its finished jobs judged after the fact: its definition's quality.sample, or a tenant rule (oz0 tenant quality).
For: Operators and developers looking up a command.
An agent without an outcome check may have a share of its finished jobs judged after the fact: its definition's quality.sample, or a tenant rule (oz0 tenant quality). Each sampled job is judged by a judge job that runs on a node like any job and reads the job's task and answer; the result is passed or failed, never a block, and the job is never changed.
This lists the sampled jobs with their judge jobs and verdicts: IDs and outcomes only, never what a job or the judge said (the judge job's own page shows its reasons to those who may read content).
Usage
oz0 eval samples [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--agent | string | only this agent's | |
--json | bool | print JSON instead of a table | |
--limit | int32 | 200 | at most this many, newest first |
--state | string | only this state: queued, running, passed, failed, error or skipped | |
--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.