Many hands. One quilt.
Your repo is a quilt. Each agent sews its own square, and the server stitches squares into main one patch at a time, so two agents never write over each other.
$ npm install -g @heyquilt/seamgit: repositorygit: branchgit: merged commitgit: sparse checkoutSquares in, patches out
Every agent works at once. The server merges each square the moment it is ready, numbers it on main, and keeps a clash in the square that made it.
Open a square
Each agent or task gets its own square, started from the tip of main.
$ seam square open "Fix sign-in" --quilt my-app --dir workCommit to it
Work in the block folder and commit as you would in git. Every commit is on the server the moment you make it.
$ seam commit -m "Sign-in keeps the session"Merge it
The server replays the square onto main and adds it as the next patch. No merge queue, no lock to wait for.
$ seam mergeA clash waits in its square, never on main
When two squares change the same lines, the first to merge goes in. The other keeps the clash as data, with both sides, until someone settles it with seam resolve. Main never holds conflict markers.
Every square a new patch overlaps hears about it, so its agent rebases before it goes stale.
Squares and mergingFor anyone with a repository
Seam is its own command and its own API. Quilt uses it, and so can you, your agents and your CI.
People
Import a git repo and keep working with the verbs you know.
seam import git ./my-appAgents
Each agent signs in with its own key and works in its own square.
SEAM_TOKEN=qa_… seam mergeAI tools
Every command is also an MCP tool, the same in any AI tool.
seam mcpAnything with HTTP
CI jobs and services use the same API the command does.
GET /v1/quilts/my-app/logEvery agent signs in as itself
Agents get their own keys, so each patch says which agent made it and for whom. They use the same seam commands from any cloud machine, and a webhook wakes them when a patch lands under their square.
Bring your history with you
Import a git repo and every commit on its main line becomes a patch, with its authors kept. Export it back to git whenever you like.
$ seam import git ./elegy
Imported 1335 commits (782 patches on main) into elegy (01a1705c-…).
$ seam log main~1 --quilt elegy --oneline -n 2
4d5bb0f2aacd [main:781] Session email is live: record the Cloudflare setup and what not to press
964a4f399ea2 [main:780] Session email: mail between session addresses is handed over inside QuiltSee inside your repo
Patches, squares, who made each change and what is in conflict, in one dashboard.