Show HN: Agent Council – Claude, Codex and Gemini debate code and engg questions

Convene a panel of CLI-based AI agents to deliberate on your questions. Three models answer independently, review each other's work, and the invoking agent synthesizes the verdict as chairman. Works with Claude Code, Codex CLI, and Gemini CLI. Whichever tool you invoke from becomes the chairman. The others are council members. Inspired by Karpathy's LLM Council, adapted for the CLI agent ecosystem. /council "Should we use Postgres or DynamoDB for our event sourcing system?" Dispatching Stage 1 to 3 agents in parallel... - claude (timeout: 120s) - codex (timeout: 120s) - gemini (timeout: 180s) claude responded (38.2s) codex responded (52.1s) Quorum reached (2/3). Giving stragglers 30s grace... gemini responded (64.7s) All 3 agents responded. Stage 1 complete: 3/3 successful opinions --- CHAIRMAN SYNTHESIS (claude) --- ### Consensus All agents agree: Postgres is the right choice given strong consistency requirements and team SQL experience. ### Divergence Claude emphasizes ACID guarantees as non-negotiable for account balances. Codex flags a scaling ceiling at ~10TB without sharding. Gemini suggests read replicas as a scaling bridge. ### Confidence HIGH — Strong consensus across models. Every existing LLM council is API-call-based. Karpathy's LLM Council, Perplexity Model Council, Council AI... they all pass text through API endpoints. Agent Council is different: - Grounded deliberation. Council members are CLI agents with tool access. They can grep your codebase, read migration files, rungit log . Opinions are grounded in your actual project, not abstract text generation. - Zero marginal cost. You're tapping into subscriptions you already have (Claude Code, Codex, Gemini CLI). No new API tokens to buy. - Living decisions. Every deliberation is a hypothesis that can be re-evaluated. "We chose Postgres 3 months ago... re-run with what we know now." Use /council-revisit to compare then vs now. npx cliagent-council This clones the repo, installs skills for all detected CLI agents, and you're ready to go. git clone https://github.com/yogirk/agent-council.git cd agent-council ./setup Platform: macOS and Linux. Windows users: use WSL. Requirements: Bun + at least 2 of these CLI agents: - Claude Code ( claude ) — skills install to~/.claude/skills/ - OpenAI Codex ( codex ) — skills install to~/.agents/skills/ - Gemini CLI ( gemini ) — skills install to~/.gemini/skills/ The same slash commands work in all three CLIs. The invoking agent automatically becomes the chairman. /council "Should we use WebSockets or SSE for real-time updates?" /council --with-review "Review auth middleware for security issues" /council --quick "What's the best job queue for Node.js?" /council-list # List all past sessions /council-replay council-20260329-143000 # Replay a session in terminal /council-revisit council-20260329-143000 # Re-run with current context (living decisions) /council-outcome council-20260329-143000 "It worked great" # Record outcome When invoked from Claude Code, Claude is chairman. From Codex, Codex is chairman. From Gemini, Gemini is chairman. The chairman gives its own independent opinion in Stage 1, then synthesizes all opinions in Stage 3. # Fast mode (default): opinions + synthesis bin/council --question-file question.txt --project myapp # Specify chairman explicitly (auto-detected if omitted) bin/council --question-file question.txt --chairman codex --project myapp # With peer review bin/council --question-file question.txt --project myapp --with-review # Browse past sessions bin/council list --project myapp bin/council replay council-20260329-143000 --project myapp +------------------+ | Your Question | +--------+---------+ | Stage 1: Independent Opinions | +----------------+----------------+ | | | +-----------+ +-----------+ +-----------+ | Claude | | Codex | | Gemini | | Code | | CLI | | CLI | +-----------+ +-----------+ +-----------+ | | | v v v [Opinion A] [Opinion B] [Opinion C] | | | +----------------+----------------+ | Stage 2: Anonymized Peer Review (optional: --with-review) | Stage 3: Chairman Synthesis | +------------------+ | Final Verdict | | with consensus | | and dissent | +------------------+ Stage 1: ALL agents (including the chairman) answer independently, in parallel. Each gets your question + codebase context. No visibility into what others are producing. Once a quorum of opinions arrives, a grace window starts for slower agents. Stage 2 (optional): Each agent reviews the others' anonymized opinions. Scores them on correctness, completeness, and feasibility. Produces a ranking. Stage 3: The chairman (whichever CLI you invoked from) reads all opinions (including its own from Stage 1) and synthesizes: where they agree, where they diverge, and a final recommendation with confidence level. When agents fundamentally disagree, the synthesis flags it explicitly with per-agent confidence so you can decide. Create ~/.council/config.json to customize models, timeouts, and quorum behavior: { "models": {