consensus-setup

Consensus Setup Wizard

Interactive setup to configure which AI models participate in /code-review and /plan-review.

Step 1: Check for Existing Config

Check if ~/.claude/consensus.json exists using the Read tool.

If it exists, show the user what's currently configured (list enabled models and quorum), then ask:

AskUserQuestion:
  question: "An existing consensus config was found. What would you like to do?"
  header: "Config"
  options:
    - label: "Reconfigure"
      description: "Start fresh — replace the existing config with new settings"
    - label: "Keep current"
      description: "Exit setup and keep the current configuration"

If user chooses "Keep current", print the current config summary and stop.

Step 2: Auto-Detect CLIs

Run all of these checks in parallel via Bash:

command -v pi && echo "PI_OK" || echo "PI_MISSING"

command -v codex && echo "CODEX_OK" || echo "CODEX_MISSING"

command -v agy && echo "AGY_OK" || echo "AGY_MISSING"

command -v qwen && echo "QWEN_OK" || echo "QWEN_MISSING"

Also check for an existing OpenRouter API key (verify it's non-empty):

[ -f ~/.claude/.env ] && grep -q 'OPENROUTER_API_KEY=.\+' ~/.claude/.env && echo "KEY_FOUND" || echo "KEY_MISSING"

Report findings to the user:

## CLI Detection Results

- pi CLI: {installed / not found}
- Codex CLI: {installed / not found}
- Antigravity CLI (`agy`): {installed / not found}
- Qwen CLI: {installed / not found}
- OpenRouter API key: {found in ~/.claude/.env / not found}

Step 3: Provider Choice

AskUserQuestion:
  question: "How do you want to connect to external models?"
  header: "Provider"
  options:
    - label: "OpenRouter (Recommended)"
      description: "1 API key, all 9 models via pi. Simplest setup."
    - label: "Native CLIs"
      description: "Use codex, Antigravity (`agy`), and qwen CLIs directly where available. Requires each CLI installed separately."
    - label: "Both"
      description: "Mix and match — use native CLIs where available, OpenRouter/pi for the rest."