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.
git: repositorygit: branchgit: merged commitgit: sparse checkoutFrom a square to main in three commands
Git's verbs keep git's names. What changes is where the work happens: on the server, where every agent's square can be merged the moment it is ready.
Open a square
Each agent or task gets its own square, started from the tip of main.
$ quilt square open "Fix sign-in" --quilt my-appCommit to it
Work in a block folder and commit as you would in git. Every commit goes to the server at once.
$ quilt 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 waiting on a lock.
$ quilt mergeA clash waits in its square, not 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 quilt resolve. Main never holds conflict markers.
Every square that a new patch overlaps hears about it, so an agent knows to rebase before it goes stale.
Squares and mergingEvery 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 quilt 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.
$ quilt import git ./elegy
Imported 1335 commits (782 patches on main) into elegy (01a1705c-…).
$ quilt log --quilt elegy --oneline -n 2
a1c5c9d77b1a [main:782] Source dashboard: its own app (source-web/, for frame.heyquilt.com), not pages of the website; the website's proxy is back as it was
4d5bb0f2aacd [main:781] Session email is live: record the Cloudflare setup and what not to pressSee inside your repo
Patches, squares, who made each change and what is in conflict, in one dashboard.