Coordinate AI coding agents before they edit the same files
Run two or more agents on the same codebase and the risk isn't speed — it's two of them editing the same file at once and clobbering each other. Vibsync lets agents coordinate before they write: check for overlap, claim what they're touching, and see who owns what.
claims are advisory coordination — a cooperative signal agents check before editing, not an OS-level lock or a distributed mutex. They stop well-behaved agents from unknowingly colliding; they do not physically prevent a process from writing a file. For hard isolation, pair claims with per-agent git worktrees.The collision problem
Parallel agents run on a shared filesystem and don't naturally respect boundaries. One may decide a nearby file is relevant and edit it; two may check the same file at the same moment, both think it's free, and both write. Splitting work along file lines helps, but something still has to coordinate the split and track who is touching what right now.
How Vibsync coordinates
check_conflicts— before writing, see whether the paths you're about to touch overlap another agent's claims.claim/release— announce and advisory-lock the files or directories you're editing, then release when done.- Shared task board (
create_task/claim_task/update_task) — so two agents don't start the same work.
How it compares
| Approach | What it does | What remains |
|---|---|---|
| Git worktrees | Isolate each agent's working copy | Great for isolation; doesn't coordinate who should own a file or share decisions |
| Hard file locks / mutex | Enforce exclusivity | Heavy and brittle across machines and tools; not how MCP agents work |
| Vibsync claims | Advisory coordination signal agents check before editing (lightweight, cross-machine/tool) | Cooperative, not enforced — a rogue agent can still ignore it |
Honest limits
Claims are a cooperative signal. A misconfigured or misbehaving agent can ignore a claim and write anyway. When you need strong isolation, pair claims with per-agent worktrees. What Vibsync reliably delivers is that well-behaved agents stop colliding by accident.
Connect in a minute
{
"mcpServers": {
"vibsync": { "type": "http", "url": "https://mcp.vibsync.com/mcp" }
}
}Step-by-step for each client is in the getting started guide. Related reading: How to Prevent Multiple AI Coding Agents from Editing the Same Files.