claude-council plugin

A Claude Code plugin that asks several AI models the same question and shows their answers side by side with a synthesis of agreement and divergence

  • 932 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

Why this level

  • Sends the question and attached files to external models
  • Handles provider API keys and can show uncommitted changes to a second model
All reasons and checks

hex/claude-council

Install

Works in

Manual install

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

After installing, configure at least one provider: an API key, a subscription CLI or local ollama.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Sends the question and attached files to external models
  • Handles provider API keys and can show uncommitted changes to a second model

This is third-party code. Review the repository files before installing.

What it does

The plugin consults several models in parallel to get diverse perspectives on a contested decision: architecture choice, a debugging dead end, a security review, a framework pick. It can reach Gemini, OpenAI, Grok, Perplexity, Kimi and any model OpenRouter routes to via API keys, plus the installed codex, antigravity, grok and kimi CLIs on subscription auth and a local ollama model with no key or network. Answers appear side by side with vendor-colored headers, and the synthesis separately names where the models agreed and where they diverged, and the assumption the agreement rests on. In tmux the answers stream into a side pane as they land. There are roles and a debate mode, background jobs, and an optional gate before the turn ends where a second model reviews uncommitted changes. The advise command shows exactly what would leave the machine before sending a request.

Who it is for. For developers who want a cross-check from several models before an important technical decision, not one model's opinion.

Good fit when

  • You need to cross-check an architecture decision or a technology choice across several models
  • Debugging is at a dead end and a second and third view would help
  • You need code or design reviewed from several angles at once, with roles or a debate

Not a fit when

  • Code and conversation must not be sent to external models due to confidentiality rules
  • No provider is configured: no key, no subscription CLI and no local ollama

Example request

Ask the council: for a SaaS users table, should the primary key be UUID or BIGINT

Limitations

You need at least one configured provider: an API key (OPENAI_API_KEY, GEMINI_API_KEY, XAI_API_KEY, PERPLEXITY_API_KEY, KIMI_API_KEY, OPENROUTER_API_KEY), an installed subscription CLI or a local ollama model. Requests to external providers are paid and send your question, and, when files are attached, your code, off the machine. Side-pane streaming needs tmux. From Russia some providers such as OpenAI and Gemini are unavailable without a VPN, while OpenRouter and local ollama may behave differently, so availability depends on the chosen provider.

How to disable. Uninstall the claude-council plugin via /plugin and remove the marketplace. Optionally remove the provider API-key variables from your environment.

FAQ

Which providers can I connect?

Gemini, OpenAI, Grok, Perplexity, Kimi and any model via OpenRouter by API keys, plus the codex, antigravity, grok and kimi CLIs on subscription and a local ollama model.

Does my code leave the machine?

Yes, when you use external providers, the question and attached files are sent to them. The advise command shows in advance what would leave, and local ollama runs without a network.

Discussion

No questions or reviews yet.

Plugins

A Claude Code plugin that runs one task across several external models and surfaces disagreements before you ship

PluginExtended access4.4KRepository stars

Plugin and MCP server that asks GPT, Gemini, Grok and local models to review a plan or hunt for bugs before code ships.

PluginBroad access183Repository stars

Claude Code plugin that convenes a council: members analyze alone, then cross-examine one another and deliver a verdict.

PluginMinimal access186Repository stars

A local web service and MCP server that gathers several models to answer, peer review each other or debate as advisor personas.

MCP serverExtended access142Repository stars

Claude Code supervises while Codex, opencode and pi work on your quota: delegated edits, independent review, model discussions

PluginBroad access122Repository stars
Editors’ pick

Multi-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents

PluginBroad access40.8KRepository stars

README in short

The README describes claude-council as a Claude Code plugin that queries several models in parallel and shows their answers side by side with a synthesis. Providers connect by API keys, through installed subscription CLIs or through local ollama, and configuring at least one is enough. Commands let you ask all or selected providers, attach a file or screenshot, assign roles, enable a debate and run background jobs. The synthesis separately shows agreement and divergence and names the assumption the agreement rests on. Installation goes through the hex/claude-marketplace marketplace or from a local copy via claude --plugin-dir, and side-pane streaming needs tmux. MIT license.

README badge

Report a problem