Demo

Same file, two agents

Both need src/router.ts. Flip Without / With to see conflict vs clean handoff.

Two agents. One file. Clean merge.

1
Claim
Before starting a task, an agent requests an exclusive lease on the files it expects to modify. If none of the requested paths are already leased, the lease is granted immediately.
POST /v1/leases → 201 { status: "granted", paths: ["src/router.ts", …] }
2
Queue
An overlapping request is blocked before coordinated work begins and is queued FIFO, with the blocking lease named, so waiting is visible and explainable.
201 { status: "queued", queue_position: 1, blocked_by: ["lse_…NG3GT4"] }
3
Handoff
The PR merges → a webhook releases the lease → the queue re-evaluates. In this run, the scheduler granted profile’s lease 2 ms after checkout’s lease was released. No polling, no human.
pr_merged → release → reassign · granted +2ms
4
Verify
Every coordinated PR pair is replayed using git merge-tree to verify that the resulting merges are conflict-free. The numbers on screen come from those replays and are measured, never estimated.
git merge-tree replay → 1/1 pairs, 0 conflicts