· Veripsa
Why parallel AI PRs collide on main, and what to do about it
AI coding agents can open correct-looking pull requests in parallel. The missing layer is open-PR coordination before merge.
Parallel AI coding agents can create a new coordination problem: multiple pull requests may be individually reasonable while still interfering when merged together.
This is not the same category as a normal code-review finding, a CI failure, or a merge-queue rebuild. It happens while PRs are still open, before the final merge order is clear.
Why it happens
Each agent usually works from its own branch and goal. That branch may be based on the same main revision as other agent branches. If two PRs change related structure, each PR can still look fine in isolation:
- Git may see no textual conflict.
- CI may not cover the specific interaction.
- Review may focus on the single PR being reviewed.
- A merge queue may only see the issue later, when the PR is already ready.
The gap is the relationship between open PRs.
What helps
Useful coordination tooling should appear before merge and stay advisory:
- Show the signal directly on the PR.
- Point to related open PRs when overlap may matter.
- Keep Clear, Heads up, Wait in line, and Unknown visually distinct.
- Let humans choose the landing order, with an optional acknowledgement only when they want an auditable override.
- Avoid storing source file bodies.
Veripsa Core is built for that gap. It is pre-merge collision control for open PRs in the same repository. It is not a merge queue, not an AI reviewer, and not CI.