claude-council

A Claude Code plugin that consults multiple AI coding agents in parallel and shows you their answers side-by-side. Useful when one model's bias could mislead you and the right call depends on cross-checking: architecture decisions, debugging dead ends, security reviews, framework picks.

Twelve seats answering one question in the pane inside Claude Code. Each banner names the seat, the model that answered and how long it took, and the answers fold once the synthesis lands so it sits near the top. This pane needs CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1. Inside tmux without it, the answers stream into a tmux side pane; outside both, they arrive in the chat.

Quick start · What gets sent · Commands · Providers · Usage guide · Reference

Quick start

You need curl and jq, on macOS, Linux, or Windows through Git Bash.

1. Install the plugin in Claude Code:

   /plugin marketplace add hex/claude-marketplace
   /plugin install claude-council
   

2. Give it at least one provider, in the shell you start Claude Code from:

   export OPENAI_API_KEY="..."   # or GEMINI_API_KEY, XAI_API_KEY, PERPLEXITY_API_KEY,
                                 # KIMI_API_KEY, OPENROUTER_API_KEY
   

   Or install any of the codex, agy (Antigravity), grok, kimi or cursor-agent CLIs. They use your existing subscription and need no key. A local ollama model works too, with no key and no network. With none of these, --local convenes a council of Claude subagents instead (Local council).

3. Check what it found, then ask:

   /claude-council:status
   /claude-council:ask "Should I use UUID or BIGINT primary keys for a SaaS users table?"
   

Each provider answers on its own, then Claude writes a synthesis: where they agree, where they split, and what to do. Agreement is not verification. Every provider gets the same description of a system none of them can inspect, so when they all agree the synthesis names the premise the answer rests on:

## Synthesis
All five recommend SQLite. Read that as agreement about the reasoning, not
as verification: every provider was given the same description of a system
none of them can inspect. The answer assumes this stays single-node — the
one premise that would flip it, and the one nobody here could check.

What gets sent and saved

Read this before the first question about your code.