AgentCollision
Overview
Real-time coordination overview. AgentCollision keeps parallel AI coding sessions from overwriting each other's work.
Files being edited
right now
Active chats
in last hour
Edits coordinated
in last hour
Event rate
per min, in window
Collisions prevented
last 30 days
Collision rate
in window
Chat activity
Top active chats
View all
Recent events
View all
Active chats
One card per AI coding session that has edited files in the last hour. Names and stats are inferred from the file paths each chat touches.
How this works. AgentCollision sees every file edit via tool hooks. It groups edits by which AI session made them, and names each session after its worktree directory. The numbers show how many edits each chat made, broken down by which part of the codebase was touched.
Leases
Every file edit reservation. When a chat edits a file, it briefly reserves that area of the codebase. If another chat tries to edit the same area, it gets blocked until the first one finishes.
Files
File-level leases. Each file is an independent coordination unit. Two chats editing different files run in parallel; two chats editing the same file serialize.
How file leasing works. When a chat is about to edit a file, AgentCollision resolves the file path to its git repo root, checks for an
.agentcollision/ directory, and acquires a lease on that specific file. Different files never conflict.
Events
Team activity log. Shows member joins, role changes, invites, and lease coordination events.
Searches across event type, member name, and detail. Filter chips narrow to a category: Coordination (leases, branches, conflicts), Membership, Invites, or System.
Messages
Notes your chats send each other, from any AI tool. Every message is kept.
Two parallel chats finish work and need to hand off context? Instead of copy/pasting between them, they call
agc msg send (or the legacy agentcollision.handoff.send tool). The other chat sees the message before its next edit, with no one having to pass it along. Click any thread to view the full conversation.
Loading…
Team
Coordinate across devices with your team.
Team connection
Team
--
Disconnects this device from your team. Your account and team data are not deleted. See Account for profile, password, and sign-out.
Roles
Define who can do what on this tenant. Each role bundles a subset of the 23 fine-grained scopes; assign roles to members on the Team page.
Help & reference
Concepts, keyboard shortcuts, and where to look when something breaks.
Full documentation
Guides, FAQ, CLI reference, and troubleshooting at
docs.agentcollision.comConcepts
Lease
A brief reservation on a part of your codebase. When an AI chat is about to edit a file, AgentCollision checks if any other chat is currently editing in the same area. If yes, the edit is blocked (preventing a collision). If no, the reservation is granted and the edit proceeds. A reservation stays while the chat works in that area and frees when it finishes, hands the file off, or goes idle; if nothing renews it, it lapses after the lease time (30 minutes by default, set in Settings). A chat with "21 edits" simply means it made 21 file changes, not that it held 21 reservations simultaneously.
File Lease
Each file in your repo is an independent lease. Two chats editing different files run in parallel; two chats editing the same file serialize. No configuration needed.
Agent / Chat
One AI coding conversation: a Claude Code, Codex, Gemini, Copilot or Cursor chat, or any other tool connected to AgentCollision. Each chat gets its own ID, which is how AgentCollision knows which chat holds which files.
Hook
A small check your AI tool runs before every edit, file write or terminal command. It asks AgentCollision whether another chat is working on that file, and waits or stops if so. agc setup connects your tools.
Why is "Files being edited" 0 even though I have chats running?
A chat locks a file when it starts editing it and keeps the lock until its turn ends. A chat that is only reading, running commands or waiting for you holds no files. If Edits coordinated is non-zero, AgentCollision is working.
Keyboard shortcuts
Refresh all panelsR
Go to Overview1
Go to Chats2
Go to Leases3
Go to Files4
Go to Events5
Go to Team6
Go to Analytics7
Go to Account8
Go to Settings9
Toggle this help? or H
Toggle light/dark modeT
Close any modalEsc
History
Which chats were most active, what they did and what you asked them. Read from your chats' logs on this computer; nothing here leaves it.
Team Analytics
See the ROI of coordination: conflicts prevented, contested files, activity patterns.
Account
Who you are to AgentCollision, and your sign-in.
Identity
—
Solo
Profile
Avatar
Click your avatar to upload an image (it'll be cropped to a square and resized to 128×128). PNG, JPG, or GIF. Max ~100KB.
Display name
Shown alongside your activity. Optional.
Email
--
Changing your email sends a confirmation link to both addresses; the change applies once you click the link in your new inbox.
Connected accounts
Loading connected providers…
Password
Change password
Update the password you use to sign in. You’ll be signed out after a successful change.
Two-factor authentication
Enable two-factor authentication
Add an extra layer of security. You’ll be asked for a 6-digit code from an authenticator app (Authy, 1Password, Google Authenticator) each time you sign in.
Browser sessions
These control your dashboard login — the browser cookie that proves it’s you. To manage installed daemons (per-machine), use the My machines panel.
Sign out of this browser
Ends your dashboard login here only. Other browsers, the CLI, and your installed daemons all keep working.
Sign out everywhere
Ends every active dashboard login across all browsers AND invalidates every API token your account has minted. You’ll have to sign in again wherever you use the dashboard, and re-mint any API tokens. Daemons authenticated via
agc login may need to be re-linked too.Danger zone
Delete my account
Permanently removes your login, clears local session data, and unlinks you from any teams. Team data (other members, their leases, audit log) is preserved. This cannot be undone.
Billing & Plan
Your plan, usage, and subscription.
Current plan
—
Current plan
Loading…
Members
—
Usage (today)
—
Machines
The computers you've connected to AgentCollision, and the team key that shows their real file names.
This machine
This machine
You're viewing the dashboard from the AgentCollision app on this computer. To see all the computers on your account in one place — and connect more — open the hosted dashboard, or run these on another machine:
1.
curl -fsSL https://install.agentcollision.com | sh
2.
agc login
The full machine list, rename, and revoke controls live on the hosted dashboard once you're signed in.
File Path Decryption
Decryption status
Checking...
Team key
Decrypts file paths in leases. Found in
~/.agentcollision/team.toml as hmac_key_b64. Or run agc team dashboard to auto-fill.Auto-import
If AgentCollision is running on this computer, click below to fetch the key. It never leaves this computer.
Or paste manually
Settings
How AgentCollision runs on each of your computers: separate work folders, protection, git, coordination and logging. A setting your team has locked shows 🔒 and can't be changed here.
SettingsIntegrations
How AgentCollision runs on this machine. Changes save as you make them.
API tokens for developer integrations, CI, and custom scripts. (Per-machine daemon settings now live on the Machines page; company standards on the Team page.)
Integrations
API tokens for developer integrations, CI, or custom scripts. Not for adding teammates — use the Team page to invite people.
Loading…
Saved
Worktrees
Separate work folders (git worktrees) each chat gets when it starts, so parallel chats never edit the same copy of a file.
Change this in Settings. Clean up removes old ones with no unsaved changes, or run
agc worktree clean.
Loading worktrees…
Policy
Rules that block or flag what your chats may do. New rules apply on this computer right away, and the strictest rule wins.
To share rules through a repo, copy the exported rules into its
.agentcollision/policy.yaml and commit it.
Loading policy…
Priority
When an urgent task needs a file a less urgent task is holding, these rules decide whether to hand it over. Rules are checked in order; the first match wins.
Loading priority ruleset…
Protection
Everything AgentCollision has governed for you — collisions prevented, conflicts caught, branch contentions flagged, and handoffs agents brokered on their own — alongside your real AI usage (calls, tokens, and cost per chat). Coordination is captured from your live sessions; usage is read from your local Claude Code logs (Pro/Max) and
agc proxy (API-key agents).
Flagged events
Collisions, conflicts, preemptions, and bypasses AgentCollision caught — searchable and expandable.
Coordination
What every agent on the team is doing and saying: one summary per chat session (what it worked on, which files, how long), plus cross-chat messages (
agc msg send). Click a row to open it.
Loading coordination…
Sessions
Every AI chat on this machine: what it is working on, where, the files it holds, and when it was last active. Make a rule for one session, or remove one that is gone.
Loading sessions…