AgentCollision AgentCollision Docs
OPEN SOURCE

Stop AI coding sessions from overwriting each other's work.

AgentCollision runs as a single Go binary alongside your Claude Code, Cursor, Cline, or Windsurf sessions. When two agents try to edit the same file at the same time, the second one waits until the first finishes. Sub-millisecond coordination, zero config, works locally and across your team.

Install
brew install agentcollision && ac init

The problem

Without AgentCollision

  1. 8:00 — You open Claude Code on auth.ts to fix a bug.
  2. 8:01 — You open another window and ask Claude to refactor the same file.
  3. 8:02 — Both chats edit auth.ts simultaneously.
  4. 8:03 — Chat B's write silently overwrites Chat A's fix.
  5. 9:15 — CI goes red. You spend 40 minutes debugging.

With AgentCollision

  1. 8:00 — Claude Code acquires a lease on auth.ts before editing.
  2. 8:01 — Second session asks for the same file.
  3. 8:02 — AgentCollision blocks Chat B synchronously. Chat B picks a different file.
  4. 8:03 — Chat A finishes. Lease releases. Chat B can now edit.
  5. 9:15 — Both edits landed cleanly. CI is green.

How teams use it

Local

Individual developers

Install once. Every Claude Code, Cursor, Cline, or Windsurf session on your machine gets automatic coordination. Free forever.

Install locally →
Shared

Remote teams

Alice on her MacBook and Bob on his Linux box can coordinate across machines. The hosted coordinator tracks leases in real time.

Set up a team →
Zero-knowledge

Privacy-first

File paths are HMAC-hashed before leaving your machine. The coordinator never sees your code or directory structure.

How it works →

The dashboard

See every team member's active file edits, who's coordinating with whom, and catch conflicts before they happen. Runs locally at localhost:7777 or hosted at dashboard.agentcollision.com.

AgentCollision dashboard overview