oz0 replay continue

Usage and flags for oz0 replay continue.

For: Operators and developers looking up a command.

For a model or prompt change: at up to --points recorded decision points of each of up to --max-jobs finished jobs (model calls whose answer asked for tool calls), the candidate (--model, an alias or <provider>/<model>; or the agent's instructions replaced by --instructions) is asked -k times, and the unchanged control is asked -k times beside it, each with the record up to that point as context.

What they propose goes through the candidate policy (the policy now, or --preset/--policy/--promote: a proposed level change) and is never run: no tool is called.

The report gives, per decision point, the share of the candidate's answers that differ from the record and from every control answer, and the control's own share against the record (the model's own variation, which the candidate's is read against); per agent, the mean divergence. It claims nothing about the turns after a point, and nothing about the answers' quality.

These are real model calls: they run as jobs on the tenant's nodes, through the gateway, metered and under the tenant's budget and --budget-usd in all, and show as the platform's replay spend, apart from the tenant's work. A job about a data subject is never continued: its content is not sent to a model again. Starting one needs comparisons.start and the content permission; oz0 replay continue cancel ID stops one.

Usage

oz0 replay continue (--model M | --instructions FILE) --budget-usd USD [-k 3] [--points 5] [--max-jobs 20] [--since 7d] [flags]
oz0 replay continue [command]

Subcommands

Flags

FlagTypeDefaultDescription
--agentstringonly this agent's jobs
--budget-usdfloatwhat the continuation's model calls may spend in all, in dollars (required)
--instructionsstringa file of instructions that replace the agent's (at most 64 KiB)
--jsonboolprint JSON instead of a table
--k (-k)int323; 3 to 10how many times each arm is asked at each point
--max-jobsint3220, at most 200at most this many jobs, newest first
--modelstringthe candidate model: an alias or <provider>/<model>
--pluginstringonly the jobs of this plugin's agents
--pointsint325; at most 10decision points per job, spread over it
--policystringdecide under this tool-policy document (JSON) instead of the policy now
--pollduration2swith --wait, how often to look
--presetstringdecide with this preset added: a shipped one, or the name of the level change --preset-rules proposes
--preset-rulesstringa JSON list of tool rules: a proposed level change
--promotestringsdecide with these shadow rules acting
--sincestring7dhow far back to read: 7d, 36h, 90m
--tenantstringdefaulttenant
--waitboolwait for the report and print it

Inherited flags

FlagTypeDefaultDescription
--contextstring$OZ0_CONTEXT or <config dir>/orchestrator-zero/context.jsonCLI context file written by server init
--log-levelstringinfolog level: debug, info, warn or error

See all oz0 commands and the global flags.

Copyright © 2026