debate

debate v2

Get a second (and third, and fourth) opinion on your implementation plan before you write a line of code. debate sends your plan to multiple AI reviewers in parallel, synthesizes their feedback, has them argue out contradictions, and produces a consensus verdict.

v2 is a ground-up rewrite. Everything now runs through acpx — a single unified CLI that talks to any coding agent. No more managing individual CLIs, session files, or API keys per provider. One config, any combination of models.

Quick Start

# 1. Install the plugin
/plugin marketplace add STRML/cc-debate
/plugin install debate@cc-debate

# 2. Install acpx
npm install -g acpx@latest

# 3. Configure your review panel (interactive)
/debate:acpx-setup

# 4. Run a review
/debate:all

Restart Claude Code after installing the plugin.

---

How it works

You: /debate:all

Claude: Running parallel review via acpx...

  codex    → agent: codex    (120s)
  gemini   → agent: gemini   (240s)
  mercury  → agent: mercury  (120s)

  ## Codex Review — Round 1
  The retry logic in Step 4 doesn't handle the case where...
  VERDICT: REVISE

  ## Gemini Review — Round 1
  Missing error handling when the API is unavailable...
  VERDICT: REVISE

  ## Mercury Review — Round 1
  Unstated assumption: this plan assumes the temp directory is writable...
  VERDICT: REVISE

  ## Synthesis
  Unanimous: all reviewers flagged missing error handling
  Unique to Codex: retry logic gap in Step 4
  Unique to Mercury: temp directory writability assumption

  ## Final Report
  VERDICT: REVISE — 3 issues to address

Claude: Revising plan...
Claude: Re-submitting to all reviewers...

  ## Codex Review — Round 2   →  VERDICT: APPROVED ✅
  ## Gemini Review — Round 2  →  VERDICT: APPROVED ✅
  ## Mercury Review — Round 2 →  VERDICT: APPROVED ✅

  VERDICT: APPROVED — unanimous after 2 rounds

---

What you need

Required:

• acpx — npm install -g acpx@latest
• jq — brew install jq / apt install jq
• The agent CLIs for whatever reviewers you want (see Supported Agents below)

Optional:

• opencode — only needed for OpenRouter model access (DeepSeek, Mercury, Kimi, etc.) or LiteLLM proxy access (local models, self-hosted, etc.)

---

Supported Agents

These are the reviewer backends you can use. Mix and match — pick 2-4 for a useful review panel.

Built-in acpx agents

These have native Agent Client Protocol support. Install the CLI, and acpx handles the rest.

Agent name	Model	Install
codex	OpenAI Codex	npm install -g @openai/codex + OPENAI_API_KEY
gemini	Google Gemini 2.x/3.x	npm install -g @google/gemini-cli + gemini auth + GEMINI_API_KEY ¹
claude	Claude (Opus/Sonnet)	Already installed — you're running it now
kimi	Kimi (Moonshot AI)	See Kimi CLI docs
kiro	Kiro (AWS)	See Kiro docs
qwen	Qwen Code	See Qwen Code docs
cursor	Cursor	Install Cursor IDE
copilot	GitHub Copilot	gh extension install github/gh-copilot
opencode	OpenCode (default model)	npm install -g opencode-ai
kilocode	Kilocode	npx @kilocode/cli
droid	Factory Droid	See acpx docs
iflow	iFlow	See acpx docs
pi	Pi Coding Agent	See acpx docs
openclaw	OpenClaw	See acpx docs

¹ Gemini note: The Gemini CLI's stored OAuth works for direct CLI use but not for acpx's non-interactive subprocess mode. You need a separate API key. Get one free at aistudio.google.com/apikey, then add it to ~/.claude/settings.json:

"env": { "GEMINI_API_KEY": "AIza..." }

Claude note: Using claude as a reviewer means Claude reviewing its own plan — useful for a fresh-context skeptical read, but not truly independent. For independent perspectives, use non-Claude agents. invoke-acpx.sh automatically handles the nested-session guard (CLAUDECODE) required to run Claude as a subprocess.

Any model via OpenRouter (using opencode)

For models that don't have a native acpx agent — DeepSeek, Mercury, Mixtral, Kimi K2, GPT variants, or anything else on openrouter.ai — you can route through OpenRouter using opencode as the bridge:

acpx → opencode (custom agent) → OpenRouter API → any model

Prerequisites:

• npm install -g opencode-ai
• OpenRouter API key from openrouter.ai/settings/keys

Setup (one time per model):

Tip: Just run /debate:acpx-setup — it does all of this for you interactively.

Or manually:

# 1. Create a wrapper directory
mkdir -p ~/.acpx/agents/mercury