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

Revise: AI Editor Built with Agentic Coding Tools and Y.js CRDT
Revise is an AI editor for documents built from scratch over 10 months using agentic coding tools, with a custom word processor engine and rendering layer that only uses Y.js for the CRDT stack. It integrates multiple AI models including GPT-5.4 variants and Claude models for proofreading and revision.

Users Report Mixed Value from OpenClaw and ClawDBot: What You Need to Know
OpenClaw and ClawDBot, while promising AI tools for code automation, have left some users underwhelmed. This article explores key insights from a Reddit discussion on user experiences and value derived from these platforms.

Developer shares CLI tools that work well with Claude Code
A developer switched from MCPs to CLIs for working with Claude Code, finding that Claude handles CLI commands effectively due to training on shell scripts and documentation. They shared specific CLIs they use daily, including gh, ripgrep, stripe, supabase, vercel, sentry-cli, and neon.

Claude Code v2.1.144: Background Sessions, /model Scoping, and 15s Startup Timeout
Claude Code v2.1.144 adds /resume for background sessions, scopes /model to current session only, and fixes a 75s startup hang when api.anthropic.com is unreachable with a 15s timeout.