Main

Treat Governor as a long-session stabilizer:

• Turn it on for repos with noisy tool output (tests, builds, network dumps).
• Use its audit/compress commands to keep always-loaded context files small.
• Validate impact with its benchmark fixtures so you can quantify savings vs regressions.

Start with a single repo and compare one real task with and without Governor before rolling it out team-wide.

README excerpt (verbatim)

Governor for Claude Code

Keep Claude Code concise, clean, and under control.

Version 0.2.2

Compact professional output, context hygiene, tool-output filtering, and usage telemetry for Claude Code Max users.

Governor is the serious alternative to style-only token savers. It keeps the agent concise, shrinks recurring memory files, blocks noisy logs from flooding context, and adds planning guardrails for broad tasks.

The installed Claude Code command namespace is still /governor:*.

V2 Highlights

• VCLR benchmark harness: fixture-based benchmarks now score valid-context loss, decision preservation, and wrong-decision rate, not only token counts.
• Structured tool filtering: Governor preserves high-signal clues from noisy MCP-style payloads such as Burp history and Playwright network dumps.
• No-compress safety boundaries: risky source reads and code-heavy tool outputs stay intact instead of being compacted into something misleading.
• Capture-ready Caveman comparisons: the benchmark suite can now replay real captured Caveman comparator outputs when Claude CLI auth is available, while falling back cleanly to reference text when it is not.
• Replayable Governor reference cases: the last reference-style Governor benchmark rows can now be refreshed into captured replay files instead of staying hand-written forever.

Why It Exists

Heavy Claude Code users do not only burn quota on long answers. The bigger session killers are often:

• bloated always-loaded context such as CLAUDE.md, notes, and rules
• huge Bash/test/build output copied into conversation context
• vague prompts that trigger broad scans and repeated failed attempts
• scope drift during long coding tasks
• compactions caused by preventable context growth

Governor attacks those system problems while keeping the interaction professional and readable.

Early Results

These are directional pilot results, not universal claims.

Same machine, fresh Claude CLI Sonnet sessions, same multi-turn task, same

FAQ

Q: Is Governor a prompt or a plugin? A: README describes it as a Claude Code plugin with a /governor:* command namespace.

Q: How do I install it? A: Run bash install.sh --force, restart Claude Code, then use /governor commands per README.

Q: What problem does it solve? A: Compact output, context hygiene, and tool-output filtering to reduce quota burn (per README).