Price terms as published
Each line is the vendor’s own wording, split from the price capture checked on 2026-10-19. Nothing here is rounded, converted or re-worded — the full sentences stay in the review below. Lines that carry only a price continue the plan named on the line above, in the vendor’s own order.
| # | Plan / term | Checked |
|---|---|---|
| 1 | Free (open source, MIT per README) | 2026-10-19 |
One-liner: Gitai is a version-control system rebuilt around coding agents: it forks Gitaly,
swaps hex object IDs for content-derived semantic digests, gives every agent run its own branch
namespace, and records the agent’s mission in a gitai.yaml committed at the repository root.
This page is compiled from the project’s repository and README only. It is not a hands-on test: we have not run gitai against a repository, so nothing here is a usage claim, and no score is assigned.
Verified facts (GitHub API and README, captured 2026-10-19)
| Attribute | Value |
|---|---|
| Repository | feder-cr/git-ai |
| Stars / forks | 2,310 / 259 (GitHub API, 2026-10-19) |
| Created / last push | 2026-10-15 / 2026-10-18 |
| Primary language | Go |
| Topics | ai-agents, coding-agents, git, golang, scion, version-control |
| Stated licence | README: “Forked from Gitaly, MIT licensed”; the API’s licence field reads NOASSERTION because the LICENSE file carries combined copyright lines (gitai contributors 2026, GitLab Inc. 2016-present) |
| Price | None published — no paid tier, hosted service or price list appears in the README or repository as of 2026-10-19 |
| Install paths | npm i -g @fedcr/gitai (README: current version 0.1.10, breaking 0.2.0 next) or a shell installer that drops a binary into ~/.local/bin/gitai |
| Windows support | WSL2 or Docker, plus an experimental Git for Windows preview distributed as a .zip with no installer |
| First version | 2026-07-30, per the README’s history line |
What it changes, structurally
Four differences are documented in the README, and each one is aimed at agents rather than at humans typing commands:
- Semantic object IDs. Git’s 12-digit hex SHA-256 object IDs are replaced with a 32-byte content-derived semantic digest. The repository keeps its history; the identifier stops being opaque to the tooling that reads it.
- Branch names that encode intent. Every agent run gets
agent/<mission>/<n>oragent/<attempt>/<n>, so a repository with six concurrent agents shows who was doing what instead of one pile offeature-branch-2names. - A mission manifest in the repo. Each branch opens with
gitai.yamlcommitted at the root — the instructions the agent was given travel with the branch instead of living in a chat window. - Agent-labelled commits with human-released tags. Commits carry an
Agent:field, worktrees stay isolated per agent, and tags plus semver are reserved for human publishers, which keeps release decisions out of the agents’ hands.
The repository also states that artifacts are pushed to a separate OCI registry and linked by
digest (the README names registry.gitai.dev/missions for public projects), and that Develocity
provides the observability API. Those two lines are read from the README; we have not exercised
either endpoint.
Where it sits relative to Anthropic’s Scion
gitai’s GitHub homepage field points at Anthropic’s engineering post Redesigning source control
at Anthropic (published 2026-10-13), which describes Scion — Anthropic’s in-house, server-centred
version control — and the five-month migration off Git, done while the volume of code merged per
day grew roughly tenfold. Scion is Anthropic’s internal system; gitai is the public, open-source
attempt at the same problem space, and the repository’s own scion topic says it is tracking that
work. The practical distinction for a reader: one is a company’s internal platform, the other is a
CLI you can install today.
Who it is for
Developers running Claude Code, Codex or similar coding agents on repositories they care about —
especially anyone who has opened git status after an agent session and could not tell which
branch belonged to which task. If your agents already work in isolated worktrees, gitai’s contribution
is the bookkeeping layer: labelled commits, per-run branches, and a mission file that explains the
branch to whoever reads it six weeks later.
Honest limits
- No hands-on run is behind this page. Everything above comes from the repository’s own text.
- The licence line needs reading, not assuming: the README says MIT, while the LICENSE file carries combined gitai and GitLab/Gitaly copyright notices, so check it before embedding gitai in a commercial product.
- Version 0.1.10 with a breaking 0.2.0 announced means the command surface can still move.
- No hosted service, no uptime commitment, no pricing page. “Free” here means the source is published, not that a service is being given away.
Sources
- GitHub API,
feder-cr/git-airepository metadata — captured 2026-10-19 (stars, forks, dates, language, topics, licence field). - README.md,
feder-cr/git-ai,mainbranch — raw file captured 2026-10-19 (semantic IDs, branch scheme,gitai.yaml,Agent:commits, install commands, registry and observability lines, first-version date). - LICENSE,
feder-cr/git-ai,mainbranch — captured 2026-10-19 (combined copyright notices). - Anthropic engineering, Redesigning source control at Anthropic — published 2026-10-13; indexed copy read 2026-10-19 (Scion context only; it is not a source for gitai’s own numbers).
- Third-party cross-check status: trade coverage of the repository is indexed (explainx.ai, Medium, dev.to, The New Stack, 2026-10-18 to 2026-10-19), but the explainx.ai article URL returned HTTP 404 when fetched on 2026-10-19, so no third-party figures are quoted on this page. The numbers above are first-party only until a third-party capture is available.