oz0 tenant offload

Usage and flags for oz0 tenant offload.

For: Operators and developers looking up a command.

A tool result whose text weighs more than a job's threshold (estimated tokens) is kept as a file of the job's tree, readable only by that tree, sealed and erased with its jobs, and the model reads a stub instead: the result's size and an outline made without a model, with oz.read_result to read a section, a range of lines or a view of it. Cards, the job's history and its trace keep the whole result.

--default is the threshold of an agent whose definition sets no offload: a number of tokens, off, or platform for the platform's default (10000 tokens, provisional until measured). --ceiling is the most an agent may set, and what an agent's offload: off becomes: a number of tokens, or none to let agents set any threshold or turn offloading off. Without flags it shows the settings in effect.

The settings are part of the tenant's tool policy, so a change takes --reason (or $OZ0_REASON) as any tool-policy change does. Jobs that are running keep the threshold they started with.

Usage

oz0 tenant offload <tenant> [flags]

Flags

FlagTypeDefaultDescription
--ceilingstringthe most an agent may set, and what its off becomes: tokens, or none
--decision-refstringthe decision or case the change follows, such as a case number (at most 200 characters)
--defaultstringthe threshold of an agent that sets none: tokens, off, or platform
--jsonboolprint JSON instead of a table
--reasonstringwhy, required for every governance change (at most 500 characters; default $OZ0_REASON); the audit log keeps 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.

On this page
Copyright © 2026