oz0 plugin change-budget

Usage and flags for oz0 plugin change-budget.

For: Operators and developers looking up a command.

Show an installed plugin's change budget: at most max changesets that agents propose or apply to it within a period (3 in 7 days by default), and none for a cooldown after a rollback of it (72 hours by default: a rollout of it rolled back or aborted, or a changeset of it rolled back with oz0 changes rollback).

A changeset counts when its approval is about to be asked and when its apply call succeeds; a merge on the forge happens outside the platform, so it is not what is counted.

Past the budget, in a cooldown, or while approvals of the plugin's changes look rubber-stamped (an approval_pattern finding is open for the queue that decides them, which holds the budget at one changeset waiting for a decision at a time), a new agent-made changeset is refused before its approval is asked, its job ends with the reason, and a change_budget finding about the plugin opens (oz0 eval findings --kind change_budget).

Change the budget in the plugin's configuration (agent_changes: in oz0 plugin config export and apply, or the Configure tab): more changes, a shorter period or a shorter cooldown loosens a governance control, so it takes a reason and another admin approves it. Lists jobs and agents, never a person. Takes settings.read.

Usage

oz0 plugin change-budget <plugin> [flags]

Flags

FlagTypeDefaultDescription
--jsonboolprint JSON instead of a table
--tenantstringdefaulttenant

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