oz0 model map
For: Operators and developers looking up a command.
A mapping rule sends what an agent's definition asks for (an alias, <provider>/<model>, or every model of a provider with <provider>/) to another model, for the whole tenant, one plugin (--plugin) or one agent of a plugin (--plugin and --agent). The most specific rule wins: an agent's over its plugin's over the tenant's, then an exact source over <provider>/. A rule is applied once: its target is an alias or a model, never another rule.
A rule is checked when it is set against every agent of the tenant's plugins it reaches: what each needs, its harness's model formats and the tenant's data rules. A rule that reaches no agent, or does not fit one, is refused with the reason. Rules apply to jobs that start after the change; a job keeps the model it started on, and its trace says which rule chose it.
A rule that no longer fits when a job starts (a provider removed, a data rule tightened) fails the job before any model call; it never falls back to the agent's own model.
The plugin itself is untouched: its signature, pins and updates stay as they are, and its page says the model was changed by the tenant.
Usage
oz0 model map [command]
Subcommands
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.