Agent coordination: parallel agents that don’t overwrite each other
With several agents in one project, the usual trouble is two of them changing the same file at once, or one not knowing what the other decided. AgentVera does two things: it notices agents touching the same file and warns about it, and it gives every agent group a shared board.
File conflict warnings
When an agent edits a file it claims it for a while: as long as the agent is working, or for 10 minutes after its last edit. If another agent in the same project edits that file, nothing is blocked; the agent gets context and you get a notice.
- Same folder: an “A and B are on the same file” warning, since the changes can overwrite each other.
- Different worktrees: a note that merging may conflict.
- Claude Code is warned before the edit: it is told to re-read the file, change only what its own task needs and not undo the other agent’s changes.
- Codex’s edits are read from its conversation when its turn ends, and the conflict is reported to you.
- Each file and agent pair is reported once; claims are released when an agent stops.
Group boards
Every agent group has its own board; agents outside a group share the project board. Agents read the board, post entries and close todos with the agentvera-board MCP tools. The server’s instructions tell agents to read the board when they start, post their decisions and findings, and not take over another agent’s role.
- Entry types: Note, Decision, Todo, Finding, File / module.
- board_read filters by type, text or open todos; board_post adds an entry; board_update closes a todo or changes its text.
- In the Board tab of the right panel you can leave notes yourself, mark todos done or delete entries.
- The board is added to agents that take MCP servers: Claude Code, Codex, opencode, Copilot, Qwen Code, Goose and Amp.
Approvals and limits
Board tool calls have their own “Ortak pano” (shared board) category in auto-approval rules, so you don’t have to approve every post. Boards and file claims live on your computer. Conflict warnings compare only agents in the same project and don’t cover remote runner agents.
How to use it
- 1
Put agents that work in parallel into a group; the group gets its own board.
- 2
Give the agents their work; the instructions to use the board come from the MCP server.
- 3
Open the Board tab in the right panel to follow entries and leave notes when needed.
- 4
When a same-file warning appears, move one agent to other work or to a worktree.
Questions
Does a conflict warning block the edit?
No. Nothing is blocked; the agent gets context and you get a notice.
Do agents in different projects conflict?
No. Only agents in the same project are compared.
Where are board entries kept?
On your computer, in one file per board, with up to 500 entries per board.
Are agents on a remote runner included?
No. File conflict warnings don’t cover remote runner agents.
Related features
Bring your agents to one desk.
Start on the free plan. Download it, add a project folder and open your first agent.