Invite your team

Coordinate across multiple developers' machines. Alice on her MacBook and Bob on his Linux box will see each other's active file edits and avoid conflicts in real time.

Prerequisites

• A Team or Enterprise subscription (both include a 14-day trial, no card required)
• You're signed into dashboard.agentcollision.com

1. Send invitations from the dashboard

Open the Team tab in the dashboard. Under Invite members, enter one or more email addresses (comma-separated) and click Send invites.

Each teammate receives a branded email from noreply@agentcollision.com with a one-click accept link. The link is single-use and valid for 7 days.

2. Teammate accepts the invite

Clicking the link opens a branded accept page on dashboard.agentcollision.com/accept. They:

1. See the team name and inviter
2. Set a password (email is already verified — the invite itself is proof of email ownership)
3. Land on their dashboard with their install command ready to copy

3. Teammate installs the daemon

They copy the one-line install command from Settings → My Machines and paste it into a terminal:

curl -fsSL https://install.agentcollision.com | sh -s -- --token=THEIR_TOKEN

As soon as their daemon sends its first heartbeat, their machine card flips to Active and they appear on your Team page. Done.

Admin tasks

Manage pending invites

On the Team page, under Pending invitations:

• Resend — re-emails the same invite link
• Revoke — invalidates the link (recipient gets "invitation no longer valid" if they click it)

Change a member's role

In the members list, click the role dropdown next to a name to toggle between member and admin. Admins can invite, remove, change roles, and edit coordination policy.

Remove a member

Click Remove next to their row. Their install tokens are revoked immediately; their daemons start getting 401s and stop syncing.

Set coordination policy

On the Team page, the Coordination policy section lets admins tune:

• Cooldown duration (0–300s) — wait after a lease releases before another agent can acquire
• Lease TTL (60–86400s) — how long leases stay valid without heartbeats
• Orphan detection threshold (30–3600s) — when a dead lease gets reclaimed

Changes propagate to every member's daemon within 5 seconds. No restart needed.

API tokens for CI / scripts

Settings → API tokens creates Cloudflare-style tokens you can paste into CI or scripts. They have scopes, optional expiration, and can be rolled in place. API tokens are for integrations — not for daemons. Use an install token for each machine.

Active-machine caps & multi-laptop use

Each tier limits concurrent active machines per user, not the number of machines you install on:

• Free: 1 active machine
• Team: 2 active machines per user
• Enterprise: 5 active machines per user

Install the daemon on as many machines as you want. Only N hold active coordinator slots at once. If you open a new daemon while at the cap, the oldest-active one is bumped into a 2-minute cooldown (newest-wins). This prevents token sharing without punishing real users switching between a laptop, desktop, and remote dev box.

What your team gets on the hosted dashboard

• Coordination feed — what every agent on the team is doing and saying. Decisions (lease auto-stubs that crossed the threshold) plus cross-chat messages.
• Cross-chat messaging — agents on different machines can agc msg send each other. Same-team via teamsync; cross-org via JWS-signed A2A federation.
• Multi-repo view — the daemon tracks which repos each agent is working in. Filter the Coordination, Leases, and Spend pages by repo with one click.
• Human-presence leases — install the VS Code extension on each machine and the daemon refuses agent writes to files a human has open.
• Webhooks & Slack — subscribe external systems to lease, policy, and spend-cap events. Slack incoming-webhook URLs auto-format as Slack messages with no relay process.
• Spend tracking — agc proxy records per-agent token spend; the Spend page aggregates across machines.
• Audit log — every member action recorded with hash-chained ledger entries for compliance.

Leaving or deleting

Leave a team — as a member, go to Settings → My account → Leave team. Your install tokens are revoked on that team; the account itself is untouched.

Delete the team — admins can delete from the Team page's danger zone. Permanent and irreversible. Removes all member tokens, lease state, audit log, and pending invites.

See also

• Privacy model — how we stay zero-knowledge
• FAQ — common team questions
• CLI reference — agc command surface