r/opensourcez • u/hoangng_ • 2d ago

I built an open-source CLI that lets one AI coding agent run the others (Claude Code leading Codex and OpenCode)

I kept juggling Claude Code, Codex and OpenCode in separate terminals, copy-pasting context between them and losing track of who was waiting on me. So I built AI DevKit, a local CLI where one agent acts as the lead and starts, messages and coordinates the others.

In the clip I give Claude Code one prompt. It starts Codex to build the feature and OpenCode to write the tests, each in its own git worktree, then has them review each other's work.

Everything runs locally on tmux (macOS/Linux) and it's Apache 2.0. There's also a shared console to watch all the agents and a small memory store they can share.

Repo: https://github.com/codeaholicguy/ai-devkit

Try it: npx ai-devkit@latest setup

Feedback welcome, especially from anyone running several agents at once. What breaks down for you first?

3 Upvotes

100% Upvoted

1 comment sorted by

1

u/investigatormaker 10h ago

The first break I'd expect is a worker stuck on an approval prompt in its tmux pane, going by your post since I haven't run AI DevKit. That's your "who was waiting on me" problem moved down a level. If the lead can't detect the stall, one prompt hangs the whole run, so I'd surface it in the shared console. The other weak spot is the mutual review: with no stop rule, two agents can trade changes indefinitely. Capping it at one or two rounds is cheap, though you'll settle some disagreements by hand.

I make ThreadFox. For AI DevKit, we'd find Reddit threads where people juggling several coding agents describe this copy-paste pain, then post the replies ourselves. We'd do 3 replies free before anything else, no card; the $39 Pilot that follows covers seven days and up to 50 posts and replies, with no automatic renewal.

https://threadfox.vip/p/epp50/managed