Most "multi-agent" tools assume you're running two or three agents in parallel. We built these because we're running thirty — and the usual advice (be careful, use branches, review diffs) stops working around agent number five.
At that point you need actual infrastructure: isolation, locking, orchestration, and a way to see what every agent is doing without opening thirty terminals.
Everything in this org is open source and MIT-licensed.
🛡️ GitGuardexRun many Codex & Claude agents in parallel without them overwriting each other. Isolated worktrees, file locks, PR-only merges. Auto-wires Oh My Codex, Oh My Claude, OpenSpec, and Caveman into every worktree.
Tutorial ·
|
🐜 ColonyLocal-first coordination substrate for fleets of coding agents. A SQLite store at
|
Multi-account Codex worker pool with tmux dashboards, a force-claim dispatcher, and auto-rescue supervisors. Steer dozens of parallel Codex sessions from one terminal.
|
🔑 authmuxMulti-identity helper for the Codex CLI. Auto-detects
|
Long-running Claude Code agent that tends the file-based memory lane in a real-time tick loop — keeps user, feedback, project, and reference memories tidy and de-duplicated across sessions.
|
Claude Code / Codex skill that scans
|
🪨 Recodee Rust orchestrator for running dozens of coding agents — shipping soon
🤝 Handoffs Smoother flows for when an agent hits its usage limit mid-task
🧩 OmX / OmC Deeper integrations with Oh My Codex & Oh My Claude
🧠 Memory lanes Cross-agent, file-based memory that survives session resets
📊 Observability One pane of glass for every active agent, worktree, and account
react-grab · oh-my-codex-colony · open-design · copydesingskill · seomachine · medusa-plugins · codex-plugins
Issues and PRs welcome on any repo above — we read every one. If you're also building multi-agent tooling, we'd love to compare notes: open an issue on the most relevant project.
One must imagine a multi-agent system happy.
🪨 The boulder never stops.