Gaitro and GitHub, for code agents write
GitHub is where most code lives, and pull requests were made for people reviewing people. Gaitro is made for when agents write most of the code, several work at once, and the person deciding what ships may not read code.
| Gaitro | GitHub pull requests | |
|---|---|---|
| The unit of work | A draft, opened from a request in plain words | A branch and a pull request |
| When agents would collide | Before they write code: each agent claims the functions, routes and tables it will change, and a second agent waits or asks to go first | At merge time, as conflicts in files |
| Reviewing a change | A summary in plain words, what changed, and checks written as sentences | A line-by-line diff, comments and CI results |
| Tests | Checks are sentences; the agent writes each one's test; every run gets a fresh sandbox | CI workflows you configure |
| When two changes overlap | A Choice: each way it could go, side by side, and a person picks | Someone resolves the conflict in the files |
| Going live | Nothing ships until a person presses Ship it; any earlier version comes back in one click | Merge to the main branch; undo with a revert |
| Agents | Bring Claude Code, Codex or Cursor; a CLI and MCP server built for them | Agents work through Git and GitHub's tools |
| What agents learn | Fixes proven in other projects reach your agent when a check fails | Not built in |
| Who it's for | People directing agents, whether or not they read code | Developers, and the open-source world |
When GitHub is the better fit
Open-source projects with outside contributors, teams of developers reviewing each other's code line by line, and anything that depends on GitHub's issues, Actions or marketplace. It has the biggest community there is.
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 any project can be cloned and kept in step with a copy elsewhere. Bring an existing repository in with gaitro init. We build Gaitro in Gaitro, and keep a copy of its code on GitHub.