Land, don't queue.1
The server commits, checks conflicts per path and moves the branch once per batch, so agents don't wait in line. Measured on one laptop with git/git's history; git gets its best case, a local bare repository.
200 agents landing on one branch
Clone git/git, 82,443 commits
CI reads one file, no clone first
Apple M4, release builds, method and scripts in the repository. No errors from 16 to 5,000 agents. Where git wins, too: the benchmark page.
How it works
- An agent sends the files it changed.Over the CLI, plain
git push, an SDK or MCP. No clone of history needed. - The server checks only those paths.If the branch moved but nothing touched your paths, the server rebases for you. If it did, you get the reason and the paths.
- The branch moves once per batch.Every queued change lands with one compare-and-swap. A conflicting change fails alone; the rest land.
Beside GitHub, or instead of it
- Mirror
pando mirrorpushes every landed change to GitHub, GitLab or Bitbucket, so CI and everything else keep working. Stop it to roll back. Mirroring - Migrate
pando migratebrings history, open pull requests and issues from GitHub in one command, andpando export-gittakes the history back any time. Migrating
For agents: a URL and a token
Agents read, search, write and land files over the Model Context Protocol without cloning anything. Each token is scoped to repositories, a role and an expiry, and every action is in the audit log.
claude mcp add --transport http pando https://mcp.example.com/mcp \
--header "Authorization: Bearer $PANDO_TOKEN"
Claude Desktop, Cursor, ChatGPT, Gemini CLI and other MCP clients take the same URL and header. Inside a workspace, claude mcp add pando -- pando mcp runs the tools locally. Agents and MCP
Open source, open protocol
- Apache-2.0, the whole serverNo open-core gate and no feature flags behind a licence. The protocol is published, so anyone can build a client or a server.
- Run it yourselfSQLite, Postgres or CockroachDB for metadata; disk, S3, GCS or Azure for files. OpenID Connect sign-in included.
- Tested by simulationEvery CI build runs 200 seeded simulations of replicas crashing mid-land; a nightly job explores 50,000 more. Chaos tests kill real replicas. Testing
Maintained by one person, in the open. If Grovedock stops, your history exports to git with identical trees.
Grovedock Cloud is coming.
The same server, run for you. Cloud opens first for teams in India, with a free tier for up to 3 people and 10 active agents. Elsewhere, self-host with paid support today.