Skip to the demo

The MVP at work, replayed from a real run

Same edits. Conflict · Clean merge — watch the difference.

Both agents need src/router.ts. Toggle between Without Managent (uncoordinated → real merge conflict) and With Managent (coordinated demo replay → 0 conflicts on that pair). Every lease ID, elapsed stamp, queue position, and verifier banner is captured verbatim from an actual run; playback is slowed for humans. Numbers on this page are demo/replay evidence, not a published benchmark.

With Managent · demo replay

Two agents. One file. 0 conflicts in this replay.

Captured coordinated run: exclusive leases queue the overlap, hand off in milliseconds, then git merge-tree verifies the pair. The 0-conflict banner is demo/replay evidence from that run — not a published benchmark.

With Managent (demo replay): agent A is granted an exclusive lease on src/router.ts, agent B is queued with the blocking lease named, A merges PR 101, the lease auto-releases, B is granted 2 milliseconds later, merges PR 102 cleanly, and the verifier replays the pair: 1 of 1 pairs replayed, 0 conflicts. That 0-conflict banner is captured demo evidence, not a published benchmark.

verifier: waiting for both PRs to land…

What just happened, mechanically

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 agent-b's lease 2 ms after agent-a'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

Honest edition: MVP enforcement combines an advisory lease, drift detection at PR time, and merge-replay verification — no filesystem sandbox. Within respected leases, conflicts are impossible by construction, and the replays measure the outcome. Published residual rates come from verification runs, never estimates; the scene above is one captured demo replay.

Run it on your repo

Wrap any agent command in a lease, or let Claude Code coordinate on its own over MCP. One server, your whole fleet.

# every agent task runs inside a lease

$managent run --repo acme/webapp --task "Add /profile route" \

--paths src/router.ts,src/pages/profile.ts \

--wait -- claude -p "add the profile route"

# or let Claude Code hold its own territory

$claude mcp add managent -e MANAGENT_API_KEY=mgt_live_… -- managent mcp

Managent is invite-only during early access and free while we onboard design partners.

We onboard a few fleets each week, in order of request.