Gaitro and Graphite, for code agents write
Graphite helps developers split work into stacks of small pull requests on GitHub, review them faster, and merge them through a queue. Gaitro is a repository of its own, made for agents that work at the same time and a person who decides what ships.
- The unit of work
Gaitro
A draft, opened from a request in plain words
Graphite
A stack of small pull requests, each building on the one before
- Where the code lives
Gaitro
In Gaitro, as a Git repository you can clone
Graphite
On GitHub: Graphite works on top of your GitHub repositories
- When agents would collide
Gaitro
As they edit: what each agent changes is reserved for it as it saves, function by function, so a second agent that touches it hears at once and waits its turn, or asks to go first
Graphite
When branches are rebased or merged, as conflicts in files
- Reviewing a change
Gaitro
A summary in plain words, what changed, and checks written as sentences
Graphite
A review inbox and diff view made for pull requests, alongside GitHub's checks
- Testing changes together
Gaitro
Every change is checked merged with the published version before it ships, and shipping goes through a queue
Graphite
A merge queue that understands stacks
- Going live
Gaitro
Nothing ships until a person presses Ship it; any earlier version comes back in one click
Graphite
Merging pull requests on GitHub
- Who it's for
Gaitro
People directing agents, whether or not they read code
Graphite
Developers who write and review code on GitHub, in small pull requests
| Gaitro | Graphite | |
|---|---|---|
| The unit of work | A draft, opened from a request in plain words | A stack of small pull requests, each building on the one before |
| Where the code lives | In Gaitro, as a Git repository you can clone | On GitHub: Graphite works on top of your GitHub repositories |
| When agents would collide | As they edit: what each agent changes is reserved for it as it saves, function by function, so a second agent that touches it hears at once and waits its turn, or asks to go first | When branches are rebased or merged, as conflicts in files |
| Reviewing a change | A summary in plain words, what changed, and checks written as sentences | A review inbox and diff view made for pull requests, alongside GitHub's checks |
| Testing changes together | Every change is checked merged with the published version before it ships, and shipping goes through a queue | A merge queue that understands stacks |
| Going live | Nothing ships until a person presses Ship it; any earlier version comes back in one click | Merging pull requests on GitHub |
| Who it's for | People directing agents, whether or not they read code | Developers who write and review code on GitHub, in small pull requests |
When Graphite is the better fit
Teams of developers on GitHub who like small, stacked pull requests and want review to go faster. Everything stays in GitHub, so the rest of your tools stay as they are.
When Gaitro is
When agents do most of the building: several of them at once on one project, changes you want explained in plain words, checks you can write as sentences, and a person who decides what goes live, without reading every line.
Using both
Gaitro speaks Git, so a project can be cloned and kept in step with a copy on GitHub, where Graphite works. Bring an existing repository in with gaitro init.
Graphite is a trademark of its owner. Gaitro isn't affiliated with or endorsed by Graphite. Compared as of October 2026.