Run many agents at once, with every merge to main tested.
More agents means more changes to the same code. gitta tells each agent when another one changes what its work relies on, so it adapts before the merge.
Why worktrees are only half of it
Worktrees give each agent its own copy. gitta gives each agent the news that matters to it.
What changes for your team.
For the engineering lead who wants more agents without more cleanup.
- Agents adapt while they work
- An agent learns about a change that affects it while it works, before it builds on the old version.
- Clashes found before the merge
- gitta flags pairs of changes that pass their own tests and break together, before anyone merges them.
- Tested together when you merge
- Every git merge to main runs your tests on everyone’s work combined, and a merge that fails stops before main changes.
- Room to add agents
- Each check reads only its own agent’s work, so adding agents adds little work for gitta.
79.4%
of AI agent pull requests are open at the same time as another agent’s.
Across 33,596 agent pull requests on GitHub. Xu et al., 2026
Three steps, no new habits.
- 01Start agents as you do today
Claude Code, Cursor and Codex each work in their own worktree, made by any tool.
- 02gitta watches every worktree
It finds new ones on its own and tells each agent what changed under it.
- 03Merge with git as usual
Your tests run on the combined work inside git merge, and a merge that fails stops before main changes.
Try it with the agents you already run.
Install gitta, run one command in your repository, and start your agents the way you always do.
