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

Qwen3.5-9B-Claude-4.6-Opus-Uncensored-v2 Model Released with LM Studio Configuration
A merged uncensored model combining Qwen3.5-9B architecture with Claude 4.6 Opus training data is now available, with specific LM Studio 0.4.7 settings provided for optimal performance including temperature 0.7 and top K sampling 20.

Applying Claude Code's Architecture to Local 9B Models: Key Findings and Optimizations
A developer extracted architectural patterns from Claude Code's leaked source code and applied 10 optimizations to qwen3.5:9b running locally on an RTX 5070 Ti. The key discovery was that qwen3.5:9b has native structured tool_calls, and the biggest limitation for 9B models is self-discipline in knowing when to stop exploring and start producing output.

mcp-optimizer reduces token waste from idle MCP servers in Claude Code
mcp-optimizer is a plugin that addresses token waste from MCP servers in Claude Code by analyzing tool usage and generating optimized configurations. It includes four utilities: mcp-doctor for server health checks, mcp-audit for usage analysis, mcp-optimize for creating project-local configs, and mcp-to-skills for converting tools to on-demand Skills.

Agint: A Rust CLI tool that detects contradictions in AI agent instruction files
Agint is a free, open-source Rust CLI tool that scans instruction files like CLAUDE.md and AGENTS.md for contradictions, missing file references, and sync issues. It uses static analysis for structural problems and optionally calls Claude API for semantic contradiction detection.