AgentCollision · Dashboard

Welcome to AgentCollision

Multi-agent coordination is ready. Here's how to see it in action:

1

Open two AI coding sessions in the same repo

2

Start editing files in both — AgentCollision coordinates automatically

3

Watch this dashboard light up with activity

If you just ran ac init, you're all set. Activity will appear here as soon as your AI tools start editing files.

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

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.

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.

Searches across event type, member name, and detail. Filter chips narrow to specific event types.

Team

Members

Add members

Generate an invite code to add teammates.

Coordination Policy

Coordination values that every team member's daemon must match. Changes apply to all team machines on next sync (~5 seconds). Only admins can edit.

Cooldown duration

Wait time after a lease is released before another chat can acquire it. Range: 0–300 seconds. Lower is faster handoff, higher is safer.

seconds

Lease TTL

How long a lease stays valid without a heartbeat. Safety net for crashed sessions. Range: 60–86400. Default 1800 (30 min).

seconds

Orphan detection threshold

How long a lease can go without a heartbeat before it's reclaimed as orphaned. Range: 30–3600. Default 120.

seconds

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

Go to Settings7

Toggle this help? or H

Toggle light/dark modeT

Close any modalEsc

Account

Email

--

Team

--

Session

Signed in via Supabase Auth. Session persists across browser restarts.

File Path Decryption

Decryption status

Checking...

HMAC key

Decrypts file paths in leases. Found in ~/.agentcollision/team.toml as hmac_key_b64. Or run ac team dashboard to auto-fill.

Privacy

Zero-knowledge coordination. The coordinator never sees your file paths. Resources are HMAC-hashed on your machine before transmission.

Client-side decryption. Display hints are AES-256-GCM encrypted by the daemon. Only browsers with the team HMAC key can decrypt them. The key never leaves your browser.

Session storage. Your team token and HMAC key are stored in localStorage (persists across sessions). Sign out to clear them.

Daemon Settings (Per-Machine)

Daemon settings are configured per-machine via the local dashboard at localhost:7777/ui/settings. Each team member controls their own daemon.

Should match across team

Lease TTL
Cooldown duration
Orphan detection threshold

These control cross-machine coordination. If values differ, conflicts can go undetected.

Individual preferences

Log level, auto-start, telemetry
Git context injection
Worktree allocation & cleanup
Track reads, allow revoke

Safe to differ between machines. These control local daemon behavior only.

Saved

Team Dashboard

Overview

Welcome to AgentCollision

Active chats

Leases

Files

Events

Team

You're flying solo

Help & reference

Settings