Gaitro and git worktrees, for several agents at once
A git worktree gives each agent its own folder on its own branch, all from one repository. It stops agents writing over each other's files. It doesn't tell them what the others are changing.
- What it is
Gaitro
A code repository for agents' work: drafts, claims, checks and a record of who decided what
Git worktrees
A Git feature: several working folders, each on its own branch, sharing one repository
- A folder per agent
Gaitro
Yes: each agent works in its own working copy
Git worktrees
Yes: one worktree per agent
- 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
Git worktrees
When the branches are merged, as conflicts in files
- Seeing what others are changing
Gaitro
The project page shows each open draft and the files it's changing, as agents work
Git worktrees
Nothing beyond the branches themselves; you compare them yourself
- Tests
Gaitro
Checks run on each change merged with the published version, in a fresh sandbox
Git worktrees
Whatever you run in each folder, or CI after you push
- Reviewing a change
Gaitro
A summary in plain words, what changed, and checks written as sentences
Git worktrees
Each branch's diff
- Going live
Gaitro
Nothing ships until a person presses Ship it; any earlier version comes back in one click
Git worktrees
You merge each branch yourself
- Cost and setup
Gaitro
A service: free for one person, paid plans for more
Git worktrees
Built into Git: free, nothing to sign up for, works offline
| Gaitro | Git worktrees | |
|---|---|---|
| What it is | A code repository for agents' work: drafts, claims, checks and a record of who decided what | A Git feature: several working folders, each on its own branch, sharing one repository |
| A folder per agent | Yes: each agent works in its own working copy | Yes: one worktree per agent |
| 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 the branches are merged, as conflicts in files |
| Seeing what others are changing | The project page shows each open draft and the files it's changing, as agents work | Nothing beyond the branches themselves; you compare them yourself |
| Tests | Checks run on each change merged with the published version, in a fresh sandbox | Whatever you run in each folder, or CI after you push |
| Reviewing a change | A summary in plain words, what changed, and checks written as sentences | Each branch's diff |
| Going live | Nothing ships until a person presses Ship it; any earlier version comes back in one click | You merge each branch yourself |
| Cost and setup | A service: free for one person, paid plans for more | Built into Git: free, nothing to sign up for, works offline |
When git worktrees is the better fit
One person running two or three agents on tasks that clearly don't overlap, with nothing in between. Worktrees are built into Git, cost nothing and work offline.
When Gaitro is
When agents' tasks can touch the same code, there are more of them than you can keep track of, or several people direct them. You hear about an overlap in seconds rather than at merge time, and every change is checked before it ships.
Using both
Gaitro works in worktrees. Each one is a working copy: open a draft in it with gaitro start, and what that agent edits is reserved for its draft like any other.
Git is a trademark of the Software Freedom Conservancy. Compared as of October 2026.