One root. Thousands of agents.
Grovedock is an open protocol and reference server for source control at agent scale. Commits, rebases and history run on the server, so hundreds of agents land on one branch at once with no merge queue, a clone fetches only the files you ask for, and CI reads files without checking anything out. It runs beside GitHub, or instead of it.
Grovedock was called Pando until October 2026; commands and packages keep the pando name
until 3.6. The name is inspired by Pando, the aspen grove in Utah: some 47,000 trunks on one
root. A grove is many agents on one history, and a dock is where their changes land.
Start here
- Try it in 5 minutesInstall, run a server on your laptop, import a git repository and land your first change.
- Run agents on itGive each agent a URL and a token over MCP. It reads, writes and lands without a clone.
- Beside GitHubMirror every landed change to GitHub, GitLab or Bitbucket, or move history, pull requests and issues across in one command.
- Self-hostOne binary: SQLite on one machine, or Postgres and S3 behind caches. Sign-in, backups, monitoring.
- Protocol referenceEvery gRPC call in
pando.v1, for clients in any language. - Grovedock CloudA hosted Grovedock is coming. Until then, the same server runs on your own machines, with no feature gates.
Also: migrate from GitHub, the CLI reference, the server reference, and the live console demo, which simulates an organisation of agents in your browser.
How it differs from git
| git | Grovedock | |
|---|---|---|
| Clone | downloads all history | downloads one tree, lazily, only the paths you ask for |
| Commit | built locally, pushed as packs | the server builds it from the list of changed files |
Concurrent pushes to main | one wins, the rest fetch, rebase and retry | the server rebases changes that touch different files and lands them all (how) |
| Reading a file in CI | clone first | one call: pando cat main path |
log, blame, diff | need local history | server APIs; ancestry in O(log n) |
| Integrity | SHA-1 | BLAKE3, verified at every cache tier |
Where git wins: working offline with full history. Grovedock needs the server for history, commits and landing. The benchmarks give the measured numbers, the method and the limits.
Plain git keeps working against a Grovedock server through git-remote-pando; see
Coming from git.