Overview
Real-time coordination overview. AgentCollision keeps parallel AI coding sessions from overwriting each other's work.
Writes in progress
--
Active chats
in last hour
Edits coordinated
this hour
Activity (last hour)
CHAT ACTIVITY TIMELINE
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 specific event types.
Team
Coordinate across devices with your team.
Help & reference
Concepts, keyboard shortcuts, and where to look when something breaks.
Concepts
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. Reservations last only as long as the edit — typically under a second — then automatically release. 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
A single Claude Code session (or Cline, Windsurf, Cursor -- any tool that's wired up to AgentCollision's hook). Each session has a unique agent_id the daemon uses to track who holds what.
Hook
Claude Code's PreToolUse mechanism. Before any Edit/Write/Bash tool call fires, Claude Code calls AgentCollision. AgentCollision decides allow or deny. The hook is installed via ac install-hooks.
Why is "Writes in progress" 0 even though I have chats running?
Reservations only exist during the instant a file is being written. Between edits — while the AI is thinking, reading code, or waiting for you — nothing is reserved. If Edits coordinated is non-zero, AgentCollision is working. Your chats just aren't writing at this exact moment.
Keyboard shortcuts
Refresh all panelsR
Go to Overview1
Go to Chats2
Go to Leases3
Go to Files4
Go to Events5
Go to Team6
Toggle this help? or H
Toggle light/dark modeT
Close any modalEsc
Settings
Configure AgentCollision behavior. Changes are saved immediately.
Leases & Coordination
How agents reserve and share files.
Track read operations
Show all active chats in the dashboard, not just ones currently writing. Recommended: on. Gives better visibility into what each session is doing.
Allow lease revoke
Allow agents to force-release other agents' reservations. Recommended: off. Prevents one session from steamrolling another. Turn on only if you trust all sessions to be well-behaved.
Dashboard port
HTTP port for the dashboard and API. Default: 7777. Change if another service uses that port. Restart required.
Cooldown duration
Wait time after a lease is released before another chat can acquire it. Prevents rapid back-and-forth conflicts. Default: 15s. Set to 0 for fastest handoff, or higher (30-60s) for safety.
seconds
Daemon
Startup, logging, and system behavior.
Auto-start daemon
Start AgentCollision automatically when you log in. Recommended: on. Otherwise you need to run
ac daemon manually each session.Telemetry
Send anonymous usage stats (event counts, no file paths or code). Opt-in only. Helps prioritize what to build next.
Log level
Daemon log verbosity. Use info normally. Switch to debug when troubleshooting. warn/error for quiet operation.
Lease TTL
How long a lease stays valid before auto-expiring. Acts as a safety net for crashed sessions. Default: 1800 (30 min). Lower (300-600) for faster recovery from crashes. Higher for long-running tasks.
seconds
Orphan detection threshold
How long a lease can go without a heartbeat before it's reclaimed. Default: 120s. Lower (60s) catches dead sessions faster but may false-positive on slow AI responses. Higher (300s) is safer for large codebases.
seconds
Repo Context
What agents see about recent repo activity when a new chat session starts.
Show repo context on startup
Inject recent commits, busy files, and active peers into each new session's context. Recommended: on. Gives agents situational awareness before they start editing.
Detail level for agents
Controls how much repo info is injected into each new chat session. Minimal: active peers only. Standard: + recent commits + busy files. Full: + merged PRs + worktrees.
Include merged PRs
Show recently merged pull requests. Requires the
gh CLI. Skipped if not installed.Include peer worktrees
Show other git worktrees in the same repo and what branches they're on.
Look back
How far back to scan for recent activity. Default: 24h. Increase for slow-moving repos, decrease for high-activity ones.
hours
Busy file threshold
Warn agents about files changed this many times or more in the lookback window. Default: 3. Set higher if you have a lot of churn and the warnings are noisy.
changes
Scan timeout
Max time to spend scanning git history. If exceeded, the session starts without context. Default: 3s. Increase for very large repos with deep history.
seconds
Workspaces
Give each session its own isolated copy of the repo so parallel chats don't conflict.
Auto-create workspaces
Give each new session its own git worktree so parallel chats can't conflict on disk. Recommended for teams or 3+ parallel sessions. Each worktree is a full copy of the repo.
Workspace directory
Where worktrees are created on disk. Default: ~/ac-worktrees. Use a fast SSD path. Each worktree can be 100MB-1GB depending on repo size.
Branch prefix
Branches created for workspaces start with this prefix. Default: ac/. Makes it easy to find and clean up workspace branches in git log.
Enabled repos
Which repos get automatic workspaces. Use * for all repos, or list specific folder names like MyProject, Backend. Empty = disabled.
Workspace Cleanup
Automatic cleanup of workspaces when sessions end or disk gets full.
Auto-cleanup on session end
Remove a session's worktree when it disconnects. Recommended: on. Keeps disk usage under control. Dirty worktrees are always preserved.
Keep unsaved work
Never delete worktrees that have uncommitted changes. Recommended: on. Protects against accidental data loss from auto-cleanup.
Disk limit
When total worktree disk usage exceeds this, the oldest clean ones are removed. Default: 50GB. Lower for smaller disks. Each worktree is roughly the size of your repo.
GB
Saved