AgentCollision · Dashboard

Welcome to your team dashboard

No activity yet. Three steps to get coordinating:

1

Install the daemon on your computer
Go to Settings → My machines and click Install on a new machine to get a one-line install command.

2

Invite teammates
On the Team page, enter your teammates' emails to send them branded invitations.

3

Open a Claude Code session and edit code
AgentCollision hooks in automatically. Conflicts prevented, activity shown here.

Questions? See the Quickstart guide.

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

Invite teammates

Email addresses

Comma or whitespace separated.

Role

Members

▸ Developer invite code (CLI)

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

Full documentation

Guides, FAQ, CLI reference, and troubleshooting at docs.agentcollision.com

Open Docs

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 agc 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

Profile

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.

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.

Active sessions

Loading sessions…

Sign out everywhere

Ends every active session across all devices. You’ll have to sign in again on every machine.

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.

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.

Integrations

API tokens for developer integrations, CI, or custom scripts. Not for adding teammates — use the Team page to invite people.

Loading…

File Path Decryption

Decryption status

Checking...

HMAC 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 your daemon is running on this machine, click below to fetch the key automatically. The key never leaves your local network — the daemon is loopback-only.

Or paste manually

Display preferences

Install banner

If you previously dismissed the “Install AgentCollision” banner on this team but want it back, click below.

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.

Billing & Plan

—

Current plan

Loading…

Members

—

Scheduled cancellation

—

Manage subscription

Update payment method, download invoices, or cancel.

Cancel subscription

Keeps access until the end of your current billing period.

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

Loading invitation…

Loading…

Ship faster with AI agents.
Without the collision.

Team Dashboard

Overview

Welcome to your team dashboard

Active chats

Leases

Files

Events

Team

You're flying solo

Help & reference

Team Analytics

Team Analytics is an Enterprise feature

Account

Settings

Confirm account deletion

Loading invitation…

Loading…

Ship faster with AI agents.Without the collision.

Team Dashboard

Welcome to your team dashboard

You're flying solo

Team Analytics is an Enterprise feature

Confirm account deletion

Ship faster with AI agents.
Without the collision.