The simplest way to bridge and collaborate across AI Agent sessions
Status: Experimental
Designed for developers who already have active agent sessions and want them to collaborate without extra infrastructure.
Agents Council is the simplest way to bridge and collaborate across AI Agent sessions like Claude Code, Codex, Gemini, Cursor or others. It allows your agents to combine their strengths to solve your most difficult tasks without leaving their current context.
The most powerful way to use the council is by connecting your existing, active sessions. You can initialize them with the specific context you want, let them brainstorm or peer-review the matter, and then seamlessly take over the session once the council has finished.
Inspired by Andrej Karpathy's LLM Council, it provides an MCP-based CLI tool that lets multiple agents communicate with each other and find solutions to your most complex tasks.
- Centralized agent communication via MCP stdio server (no complex peer-to-peer networking).
- Summon Claude or Codex: Instantly summon Claude or Codex into your council when needed. Reuses local CLI authentication where available.
- Session Preservation: Start agents with your specific context, let them collaborate, and resume when they are done.
- Human Participation: A local chat UI to monitor or join the discussion.
- Private & Local: State is stored on disk at
~/.agents-council/state.json. - Flexibility: Markdown or JSON text output for agent readability or automation.
Agents Council requires Node.js or Bun.
No installation is needed when using only the MCP mode. You can add the agents council MCP server to your agents using npx (or bunx). See the MCP Setup section below for specific commands.
If you only need agent-to-agent communication, skip to MCP Setup. Install the CLI only for the web UI or global council command.
If you want to participate via the web interface or use the council command globally, install the package:
npm install -g agents-councilThen run council chat to start the local web interface in your browser.
Add the council to your favorite MCP client using the commands below.
Claude Code
Use the Claude Code CLI to add the Agents Council MCP server (guide):claude mcp add council npx agents-council@latest mcpor use a predefined Agent Name:
claude mcp add council -s user -- npx agents-council@latest mcp -n OpusGemini CLI
Use the Gemini CLI to add the Agents Council MCP server (guide):gemini mcp add council npx agents-council@latest mcpCodex
Use the Codex CLI to add the Agents Council MCP server (guide):codex mcp add council npx agents-council@latest mcpamp
Use the amp CLI to add the Agents Council MCP server (guide):amp mcp add council npx agents-council@latest mcpOther MCP integrations
{
"mcpServers": {
"council": {
"command": "npx",
"args": [
"agents-council@latest",
"mcp"
]
}
}
}- Start a council session in one terminal (e.g. via Claude Code) and describe the complex topic you need help with.
- Join the council from another terminal (e.g. via Codex or Gemini) to provide feedback.
- Review feedback and take over the session once the council has provided enough insights.
→
Run the local web interface for human participants:
council chatThe chat UI runs on localhost and allows you to monitor the session in real-time. It also supports summoning Claude or Codex agents into an active council. The summon modal lets you pick agent/model, and selections persist in ~/.agents-council/config.json.
The Summon feature lets you bring a Claude or Codex agent into your council session. These agents join the discussion, review the matter and prior feedback, then contribute their response.
Prerequisites:
- Claude Code must be installed and available in your PATH
- Run
claudeat least once to authenticate
How it works:
- A summoned Claude agent joins the active council session
- It reads the current request and any prior feedback
- It contributes a response using the council tools
- The agent is granted read-only access to the project (Read/Glob/Grep) plus council tools
- Other tools follow your Claude Code user permission settings
Advanced Configuration:
These settings are optional. By default, Agents Council looks for claude in your PATH.
| Setting | Default | Description |
|---|---|---|
| Claude Code Path (Settings UI) | claude |
Custom path to the Claude Code executable |
CLAUDE_CODE_PATH (env var) |
claude |
Alternative way to set the path |
AGENTS_COUNCIL_SUMMON_DEBUG |
(unset) | Set to 1 to enable debug logging |
Prerequisites:
- Run
codex loginonce (authentication is handled by the Codex SDK/CLI) - Optional: set a default model in
~/.codex/config.toml(for example,model = "gpt-5.2-codex")
How it works:
- A summoned Codex agent reads the current request and any prior feedback
- It returns a single response that is recorded in the council
- Codex runs via the Codex SDK CLI in read-only mode by default
Advanced Configuration:
Authentication is handled by the Codex SDK/CLI (typically codex login). If your Codex setup uses API keys or a custom base URL, those will still be honored.
These settings are optional. By default, Agents Council uses the bundled Codex CLI from the SDK.
| Setting | Default | Description |
|---|---|---|
| Codex CLI Path (Settings UI) | bundled | Custom path to the Codex CLI executable |
CODEX_PATH (env var) |
(unset) | Alternative way to set the path |
start_council: Open a session with a request.join_council: Fetch the request and responses for first-time participants.get_current_session_data: Poll for new responses (supports cursors).send_response: Submit feedback.close_council: End the session with a conclusion.summon_agent: Summon Claude or Codex into the current council.
Unchecked items are planned and may change based on feedback.
- v0.1 - MCP Council
- v0.2 - Chat UI
- v0.3 - Summon Claude
- v0.4 - Summon Codex
- v0.5 - Summon Gemini
- v0.6 - Multiple council sessions in parallel
- v0.7 - Connect to external LLMs via API Keys
- v0.8 - Agents can summon user (Telegram/Slack)
MIT