Coding agents got good. Managing them didn't. I open-sourced the control room I built for it (MIT)
Summary
The author open-sourced o8, an MIT-licensed orchestrator that manages multiple coding agents in isolated git worktrees, with a merge gate, audit trail, and mobile approvals.
Similar Articles
Open sourcing the coding agent harness I started an year ago
The author has open-sourced a self-hosted workspace for coding agents, featuring multi-agent architecture, AST-aware ChromaDB indexing, and a UI with Git diff management.
my 3 coding agents argued about a design while i was away. two switched sides.
A maker shares early progress on a workspace where multiple coding agents (Claude Code, pi, opencode) collaborate in shared rooms, discussing design, debating, changing positions, and splitting work autonomously while awaiting human approval. They are looking for early feedback from people who run multiple agents.
I open-sourced the agent instructions I use to keep my AI agents on track.
This open-source tool provides a portable, agent-agnostic control plane for coding agents, offering consistent operating rules, phased project planning, memory, skills, and runbooks via a set of files that can be dropped into any repository.
I open-sourced the "harness" layer for AI agents: run Claude Code/Codex/Gemini with governed MCP tools (browser, editor, secrets)
Open-sourced a desktop workspace that provides a governed runtime for AI coding agents, offering 100+ MCP tools, RBAC, and a self-evolving toolbox.
Open-sourced a director/implementer delegation protocol for coding agents (Claude Code + Codex)
Open-sourced a platform-neutral director/implementer delegation protocol for coding agents like Claude Code and Codex, with schemas, adapters, and example scenarios to address trust in subagent completion reports.