I gave several AI coding agents the same repo. They broke each other's work in every isolated run, and started messaging each other when I let them
Summary
A field report on an open-source experiment testing how multiple AI coding agents share a codebase: isolated branches produced semantically conflicting but textually mergeable work in every run, while a shared working directory and a lightweight 'decision model' referee (Jev) improved coordination, and unsupervised agent-to-agent messaging emerged on its own.
Similar Articles
@alex_prompter: Two AI agents editing the same codebase will wreck each other's work unless you give them this instruction. Run two age…
A practical tip for running multiple AI agents on the same codebase: use a shared notes.md file for coordination to prevent conflicts.
I gave my AI agents email instead of better reasoning. They started fixing each other's bugs.
A developer builds a multi-agent framework where autonomous AI agents communicate via an email-like system to file bug reports and fix each other's code, highlighting the value of coordination over individual reasoning.
Lessons from months of running a mixed fleet of coding agents on the same repos
The article shares lessons learned from using multiple AI coding agents on the same code repositories over several months, covering insights on their effectiveness and challenges.
How I stopped juggling AI agents and let them talk to each other
The author describes the hassle of manually coordinating multiple AI coding agents and introduces Accord Agents, an open-source shared workspace that enables agents to discuss and review each other's work while keeping the process transparent to the human.
A clean git merge of my two agents' worktrees that failed its own tests
The author describes an experiment where merging two AI agents' git worktrees led to test failures despite clean merges, highlighting the challenges of parallel agent development without mutual awareness.