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

A 7-File Governance Layer to Prevent LLM Session Drift
A developer created a governance layer with seven files to prevent Claude from silently undoing architectural decisions across sessions. The system includes active_context.md, contracts.md, and decisions.md files with a strict execution loop.

yburn: Tool to audit and replace unnecessary AI agent cron jobs
yburn is a Python tool that audits AI agent cron jobs and replaces those that don't need LLMs with standalone Python scripts. The creator found 58% of 98 cron jobs were purely mechanical tasks like system health checks and git backups.

Adeu v1.4: Open-Source MCP for Track Changes in DOCX
Adeu v1.4 surgically injects native OOXML redlines into DOCX files, preserving formatting, numbering, and layouts. Adds footnotes/endnotes inline editing, defined term linting, cross-reference maps, and multi-level list round-tripping.

OpenRoom: A Web-Based Desktop GUI for Visualizing AI Agent Skills
OpenRoom is a web-based desktop environment where AI agents operate, featuring real-time updates to system state like diaries and files during chat interactions, plus a livestream mode for multi-bot interaction.