quorum
Cross-model audit gate with structural enforcement. One model cannot approve its own code.
edit → audit → agree → retro → commit
What it does
quorum enforces a consensus protocol between AI agents. When code is written, an independent auditor reviews the evidence. If rejected, the author must fix and resubmit. The cycle repeats until consensus is reached — only then can the code be committed.
The key principle: no single model can both write and approve code. This is the "quorum" — a minimum number of independent voices required for a decision.
Installation
Standalone (any AI tool)
quorum works without any IDE plugin. Just the CLI.
npm install -g quorum-audit # global install
# or
npx quorum-audit setup # one-shot without install
cd your-project
quorum setup # creates config + MCP server registration
quorum daemon # TUI dashboard
Works with any AI coding tool — Claude Code, Codex, Gemini, or manual use.
As a Claude Code plugin
For automatic hook integration (event-driven audit on every edit):
claude plugin marketplace add berrzebb/quorum
claude plugin install quorum@berrzebb-plugins
This registers 22 lifecycle hooks, 26 MCP tools, 29 skills, and 13 specialist agents automatically. The CLI still works alongside the plugin.
As a Gemini CLI extension
For automatic hook integration with Gemini CLI:
gemini extensions install https://github.com/berrzebb/quorum.git
# or for development:
gemini extensions link adapters/gemini
This registers 11 hooks, 33 skills, 4 commands, and 26 MCP tools. Same audit engine as Claude Code.
As a Codex CLI hook
For automatic hook integration with OpenAI Codex CLI:
# Copy hooks config to project
cp platform/adapters/codex/hooks/hooks.json .codex/hooks.json
# Enable hooks feature flag
codex -c features.codex_hooks=true
This registers 5 hooks (SessionStart, Stop, UserPromptSubmit, AfterAgent, AfterToolUse). Same audit engine as Claude Code and Gemini.
From source
git clone https://github.com/berrzebb/quorum.git
cd quorum && npm install && npm run build
npm link # makes 'quorum' available globally
CLI
quorum <command>
setup Initialize quorum in current project
interview Interactive requirement clarification
daemon Start TUI dashboard
status Show audit gate status
audit Trigger manual audit
plan Work breakdown planning
orchestrate Track orchestration (parallel execution) # v0.4.0
ask <provider> Query a provider directly
tool <name> Run MCP analysis tool
migrate Import consensus-loop data into quorum
help Show help
Migrating from consensus-loop
If you were using consensus-loop (v2.5.0), quorum can import your existing data:
quorum migrate # import config, audit history, session state
quorum migrate --dry-run # preview without changes
What it migrates:
| Data | From | To |
|---|---|---|
| Config | .claude/consensus-loop/config.json | .claude/quorum/config.json |
| Audit history | .claude/audit-history.jsonl | SQLite EventStore |
| Session state | .session-state/retro-marker.json | Preserved (shared location) |
| Evidence submission | docs/feedback/claude.md | audit_submit MCP tool |
| MCP server | .mcp.json consensus-loop entry | Cloned as quorum entry |
Your existing evidence is preserved — quorum reads from SQLite via audit_submit tool.
How it works
Without a plugin (standalone)
you write code
→ quorum audit # trigger manually
→ auditor reviews # Codex, GPT, Claude, or any provider
→ quorum status # check verdict
→ fix if rejected # resubmit
→ quorum daemon # watch the cycle in real-time TUI