Open-Foundry: A Framework for Multi-Agent Debates with Claude Code

What Open-Foundry Does
Open-foundry addresses a specific frustration with Claude Code: when it provides complex analysis, the extended thinking process remains a black box. If the conclusion is wrong, there's no way to trace which assumption failed. This framework solves that by creating multi-agent debates with fully externalized reasoning.
How It Works
You define a mission with a question and a panel of agents, each with a distinct persona and explicit "negative space" — things they refuse to do. The orchestrator picks who speaks next based on discussion dynamics, with agents challenging each other's claims across 20-30 turns. A synthesizer produces the final deliverable.
The entire process is autonomous — you can walk away and come back to a finished session. Because each agent is a stateless claude -p call, all thinking must be externalized into files.
What You Get
- A full transcript where every claim is attributed to a specific agent at a specific turn
- Orchestrator logs explaining why each speaker was chosen
- Per-agent working notes
- The reasoning process becomes a readable, searchable artifact
Human-in-the-Loop Capability
You can press Ctrl+\ at any point to pause and inject a message. In the sample session, the creator noticed all 6 agents were assuming a team with senior engineers — nobody was addressing solo developers. One intervention at turn 8 redirected the entire discussion.
Sample Session
You can browse a real session without cloning:
- Transcript — 6 agents debating "Should AI replace code review?"
- Synthesis — the deliverable
- Orchestrator log — why each speaker was chosen
What It's Not
Open-foundry is not a replacement for Claude Code CLI. If you know what to ask and want a fast answer, use Claude directly. This framework is for questions complex enough that you want multiple perspectives challenging each other — and you need to show (or audit) how the conclusion was reached.
Technical Details
- Stdlib-only Python, zero dependencies beyond Claude CLI
- Each agent has full access to all Claude Code tools, MCP servers, and plugins
- Apache 2.0 licensed
- GitHub: https://github.com/YiminYang27/open-foundry
📖 Read the full source: r/ClaudeAI
👀 See Also

Structured Claude Skill for B2B SaaS Growth Workflows
A developer has open-sourced a Claude Skill that structures B2B SaaS growth knowledge into playbooks and case studies to improve Claude's output quality. The repository includes 5 SaaS case studies, a 4-stage growth flywheel, and 6 structured playbooks.

Building and Testing an MCP Server in Claude Desktop: Architecture and Lessons
A developer shares their experience building and testing an MCP server within Claude Desktop, detailing their architecture setup and practical lessons learned about tool schemas, debugging, and limitations.

codebase-md: Tool auto-generates CLAUDE.md with git hook maintenance
codebase-md v0.1.0 scans projects to generate CLAUDE.md files with architecture detection, dependency health checks, and git insights. It includes git hooks to keep documentation fresh and supports other AI coding tools with additional config files.

Developer shares hybrid AI coding workflow: Claude for planning, local models for execution
A developer built a pipeline using Claude 3.5 Sonnet for task planning and local Qwen2.5-Coder models via Ollama for code generation, achieving 85% token reduction compared to using Claude alone.