Skip to main content
A one-page reference for the --low-token cost-saving preset. For motivation, trade-offs, and FAQ, see the low-token mode concept page.
Measured savings: ~30% on the first MNIST bench ($7.75 vs. ~$11 default, 2026-04-27). The preset since added two structural levers, Haiku routing for code-reviewer / test-engineer / oracle-qa and per-phase agent drops (Phase 1 and Phase 5), which target the ~50-60% ceiling. A second bench post-PR-C is required to confirm the new measured number; this page updates when the next bench lands. Full breakdown: Cost benchmark.

Activation

When either is on, the preset below applies. CLI flag wins over plan field if both are set.

The preset

Authoritative locations: src/zo/cli.py for _LOW_TOKEN_PRESET, src/zo/_orchestrator_phases.py for the routing tables.

Knob reference

Override flags

These compose with --low-token to fine-tune individual knobs:

Plan-level fields

Two YAML frontmatter fields complement the CLI flags:
Plan-level ## Experiment Loop section overrides individual loop fields with full granularity:
When low_token is on AND a plan ## Experiment Loop field is set, the plan field wins (the preset is a “sensible defaults” layer, not a hard clamp).

Precedence (highest first)

  1. CLI flag: --lead-model, --max-iterations, --gate-mode, --no-headlines
  2. Plan YAML frontmatter: lead_model, low_token
  3. Plan body section: ## Experiment Loop for loop knobs
  4. Low-token preset: applied when --low-token or low_token: true is set
  5. Base default: Opus, 10 iterations, supervised, etc.
Concrete examples:

Visual confirmation

When low-token is active, the ZO banner shows a [low-token] badge:

See also