feder-cr/git-ai

Maintainer? Show your league in your README

Card: your league's emblem, from Copper to Legendary

[![bestofgithub](https://bestofgithub.dev/badge/feder-cr/git-ai.svg?style=card)](https://bestofgithub.dev/repo/feder-cr/git-ai)

Flat: fits beside your other badges

[![bestofgithub](https://bestofgithub.dev/badge/feder-cr/git-ai.svg)](https://bestofgithub.dev/repo/feder-cr/git-ai)

Loading README…

Scion idea	In gitai
Always-online clients that fetch exactly what they need	`ObjectService` serves single objects and sparse trees; `graft clone` and `graft sparse` materialize only the paths you ask for.
Source control as an API: history runs on the server	Blame, path history, ancestry and code search run server-side and are memoized as derived data, computed once per commit.
Landing without a merge queue	`UserLand` rebases a change onto the current tip and lands it with a compare-and-swap; concurrent lands on one branch are batched into a single reference update.
Automatic conflict resolution	A conflicting land is resolved by a resolver you choose (any LLM provider, a deterministic tool, or none) through a versioned, vendor-neutral protocol. A model's resolution is only a proposal: it lands by itself only if the `verify.command` you configure passes on the exact tree that would land, and otherwise the agent gets the conflict package with the proposal. The deterministic rules you configure need no such condition of their own, and are verified on the exact tree as well when you turn the verification on (`verify.enabled`).
Changeset log	Every accepted reference update is recorded with its operation and actor in a dense, ordered log that clients list or watch live.
Storage core: a database and object storage, stateless servers	Each change is a changeset in a write-ahead log in SQLite or PostgreSQL, with a compare-and-swap per reference; packs live in object storage (file, S3, GCS, Azure). Server nodes are caches that any node can rebuild, so you add nodes to scale.
Test after landing, revert the culprit	`graft-verify` tests the tip, bisects a failure and reverts the change that broke it.
Monitoring agents ("superfans")	Agents follow the changeset stream and report what matters to each component, also through Slack.
Agent-friendly review	Reviews with semantic approval rules: a comment-only change can need fewer approvals than a logic change.
Agents as first-class users	Per-agent tokens, an RPC allowlist and branch policies decide what each agent may do.
Strict cache tiers	`graft-cache` caches immutable objects in daemon and regional tiers, verifying every object.

50 agents, 250 changes, no conflict resolver	classic	gitai
changes landed	100-106	200
attempts per landed change	26.5-28.7	1.0
lands per minute	264-385	1,487-1,944
p99 latency	4.4-5.2 s	1.9-2.7 s

feder-cr/git-ai

Git designed for AI agents.

Why

The Scion ideas, implemented

Architecture

Quick start

Documentation

Benchmark

Status

Community

Credits and license