Skip to main content

WhaleCouncil

Independent second opinions for AI agent workflows.

When you use a single AI model, you get a single perspective — one that can anchor on wrong assumptions, miss edge cases, or confidently hallucinate. WhaleCouncil sends your task to multiple models in parallel, collects independent responses, surfaces disagreements, and synthesizes a final report.

$ council review "Should I use Redis or Postgres for this session store?"

WhaleCouncil — reviewing with: claude, codex, gemini
────────────────────────────────────────────────────
claude   ✓  Redis for session data. Low latency reads, built-in TTL...
codex    ✓  Postgres if you already have it. Avoid infra complexity...
gemini   ✓  Depends on scale. Redis at >10k concurrent sessions...
────────────────────────────────────────────────────
⚡ Disagreement: Redis vs Postgres — codex flags infra cost, others favor Redis.
→ Key question to resolve: Do you already run Postgres in this stack?

Why

Heavy AI users constantly switch between Claude, GPT, Gemini — manually copying context, pasting outputs back, comparing results by eye. This is slow, error-prone, and easy to skip under pressure.

WhaleCouncil automates the loop:

  • One task in → multiple independent opinions out
  • No anchoring — models don't see each other's responses in the first round
  • Structured diff — disagreements are extracted, not buried in prose
  • Actionable output — synthesis points to the next decision, not a summary of summaries

The core insight: one AI versus two AI is a qualitative difference, not a quantitative one.


Install

pip install whalecouncil

Or from source:

git clone https://github.com/openwhale-labs/whalecouncil
cd whalecouncil
pip install -e ".[dev]"

Set your API keys in .env (copy from .env.example):

cp .env.example .env
# edit .env with your keys

Usage

Review a task

# inline
council review "Is this approach correct: use a global dict as a cache in a FastAPI app?"

# from file
council review --file mycode.py

# choose models
council review --models claude,codex "Review this SQL query for performance issues"

# output to markdown file
council review --output markdown --file plan.md > report.md

Pipe input

cat diff.patch | council review --models claude,gemini
git diff HEAD~1 | council review "Any bugs introduced in this diff?"

List available models

council models

Configuration file

Persistent defaults can be set in ~/.council.toml (copy from council.toml.example):

[defaults]
models = ['claude-cli']
output = 'terminal'

[models.claude]
model = 'claude-sonnet-4-6'

CLI flags always override the config file, which overrides the built-in defaults. Per-provider [models.*] entries set the model each adapter uses.


Supported Models

Key Provider Notes
claude Anthropic Requires ANTHROPIC_API_KEY
claude-cli Local Claude subscription (Claude Code CLI) No API key needed. Requires claude CLI installed and logged in.
codex OpenAI Requires OPENAI_API_KEY
codex-cli Local Codex CLI (codex exec) No API key needed. Requires codex CLI installed and logged in.
gemini Google Requires GEMINI_API_KEY
gemini-cli Local Gemini CLI (gemini -p) No API key needed. Requires gemini CLI installed and logged in.

How It Works

Input task
    │
    ├──► Claude  (independent, no other model's output)
    ├──► Codex   (independent)
    └──► Gemini  (independent)
         │
         ▼
   Collect opinions
         │
         ▼
   Extract disagreements
         │
         ▼
   Synthesize + surface next question
         │
         ▼
   Markdown or terminal report

Round 1 — Independent: Each model receives only the task and a neutral system prompt. No model sees another's output.

Round 2 — Synthesis (optional): A judge model receives all opinions and produces a structured diff: what they agree on, where they diverge, what the divergence reveals, and what question to resolve next.


Roadmap

  • CLI skeleton
  • Parallel model dispatch (asyncio)
  • Model adapters: Claude, OpenAI, Gemini
  • Disagreement extraction
  • Synthesis / judge layer
  • Markdown report output
  • Pipe / stdin support
  • Config file (~/.council.toml)
  • WhaleTrace — save and replay council runs
  • WhaleBench — structured benchmark tasks for agent evaluation

Design Philosophy

  • CLI-first — works in any terminal, composable with pipes
  • Independent opinions — first round is always blind; no anchoring
  • Disagreement over consensus — the value is in the diff, not the summary
  • Minimal infra — no server, no database, no account required
  • Extensible — add any OpenAI-compatible model endpoint

Contributing

See CONTRIBUTING.md.


License

MIT © noetherly

Release files for whalecouncil 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for whalecouncil 0.2.1
File Size Uploaded
whalecouncil-0.2.1.tar.gz 62.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for whalecouncil 0.2.1
File Interpreter ABI Platform
whalecouncil-0.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 112.1 kB

Release files / whalecouncil-0.2.1.tar.gz

Download URL whalecouncil-0.2.1.tar.gz
Size 62.2 kB
Tags Source
SHA-256 checksum
How to use checksums
81e1e17dbf15154888349c1827263e618205253d6f7818f077c3533ca802b7df
BLAKE2b-256 checksum
How to use checksums
c08d03e9577ff5ac663372b0026491fd8342d81d765eeb193defb447a83335d0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 17, 2026.

Transparency log

Release files / whalecouncil-0.2.1-py3-none-any.whl

Download URL whalecouncil-0.2.1-py3-none-any.whl
Size 49.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
98ab6bf44b248590cc2c6cf9e6e0f5ee524fc87070190818cc78f128621b1012
BLAKE2b-256 checksum
How to use checksums
eefeea861504edd04ba74fb9fd9d3c8e387dcb1d63cdd7c59b78dc6ebdfb2735
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 17, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.1 This release

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page