Skip to main content

Harness commands

Integrations

voss mcp and voss skills show what Voss discovered from Claude, Codex, and Voss config. voss shell-init prints an OSC 133 snippet that lets a terminal host such as Voss ADE see command boundaries, exit codes, and the working directory.

Judgments and evaluation

Jev judgments are opt-in and advisory. voss judge review prints a requirement assessment per criterion (supported, contradicted, unclear, or no answer); it never approves, blocks, or moves work. voss eval --ab runs the suite twice with one task setting changed and compares the results.

Project context and recall

voss recall searches project memory and the rebuildable code recall index together. Use --refresh when you want Voss to rebuild recall state before answering. voss sync --check is read-only and exits non-zero when generated docs, managed instruction sections, or prompt files have drifted.

Compiler commands

Orchestration commands

Run and inspect a team — see Orchestration.

Command boundary

Mode flags

Commands that run the harness may accept mode selection:
Default modes are conservative: plan for general harness commands and edit for scoped edit sessions. --no-pack disables context packing for the run and keeps replay assembly on the legacy full-context path.

Renderer environment

Bare voss opens the Go terminal client. These variables change that and the line renderer:
VOSS_USE_TUI=0 uses the plain line-by-line chat instead of the Go client; the plain chat is also the fallback when the voss-tui binary is missing. VOSS_TUI_BIN selects a specific Go client binary. VOSS_RENDERER=compact selects the dense line renderer for hosts that run Voss inside another terminal pane.