git-ai README

The project's README from github.com/feder-cr/git-ai. As one markdown file: README.md.

open_scion

Source control for the age of coding agents.

Anthropic built Scion, a faster version control system for coding agents, and described it in Redesigning source control: a server-centric system built for hundreds of agents that read, write and land code at the same time. Scion is internal to Anthropic and is not available to the public.

So I built open_scion: an open-source version of that design that anyone can run, and that the community can improve and maintain together.

MIT licensed. Vendor neutral: the server never calls a language model, and every AI feature works with any provider, or none.

open_scion is an independent implementation of the publicly described design. It is not affiliated with or endorsed by Anthropic.

Why

Classic Git hosting was built for humans who clone a repository, work for hours and push once. Coding agents work differently: thousands of short-lived tasks, each touching a few files, each wanting to land in seconds, all on the same branches. Full clones, merge queues and client-side history walks become the bottleneck.

Scion's answer is to move the work to the server: clients stay online and fetch only what they need, history questions are answered (and cached) by the server, changes land through a compare-and-swap instead of a queue, every update is an entry in a changeset log, and the repository state lives in a consistent database plus object storage so servers scale out. open_scion implements these ideas, with normal Git repositories underneath.

The Scion ideas, implemented

Scion idea In open_scion
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.
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.

Architecture

        agents, CI jobs, sparse workspaces          graft CLI / Go SDK
                            |
                            v   gRPC
        +-------------------------------------------------+
        |  graft-cache (optional daemon and cache tiers)  |
        +------------------------+------------------------+
                                 v
   +---------------------------------------------------------------+
   |  open_scion server (any number of nodes)                      |
   |  land - objects - changesets - derived data - search - review |
   |  write path: changeset + compare-and-swap per reference       |
   +-----------+--------------------------------+------------------+
               |                                |
               v                                v
   +-----------------------+       +-----------------------------+
   |  SQLite / PostgreSQL  |       |  object storage             |
   |  changeset WAL, refs, |       |  content-addressed packs    |
   |  changelog, reviews   |       |  (file, S3, GCS, Azure)     |
   +-----------------------+       +-----------------------------+
               \                              /
                local Git repositories = caches any node can rebuild

Details: ARCHITECTURE.md and STORAGE.md.

Quick start

Requirements: Linux or macOS, Go 1.26, a C toolchain, Meson and Ninja (the build compiles a bundled Git).

git clone https://github.com/feder-cr/open_scion.git
cd open_scion
make build                         # server, CLI and tools into _build/bin
examples/graft/quickstart.sh       # a server, a cache daemon, two agents and a land, in a temporary directory
./_build/bin/graft                 # the CLI and its commands

To run your own server, adapt examples/graft/config.toml and start it with _build/bin/gitaly serve config.toml. To put the repository state in a database and object storage, add a [graft.storage] section: start in shadow mode, import your repositories, then switch to authoritative (STORAGE.md).

Inside the code the extensions are called Graft: the [graft] configuration section, the graft CLI, internal/graft and doc/graft.

Documentation

Status

Version 0.1.0, the first public release. Everything above is implemented and covered by unit, end-to-end, multi-node, crash and fuzz tests. Interfaces may still change before 1.0. Known gaps (for example garbage collection of packs in the storage core) are listed in LIMITATIONS.md.

Community

open_scion is meant to be maintained by its community. Open an issue to report a bug or propose an idea, start a discussion before a large design change, and send pull requests: tests and a short description of the reasoning make them easy to review. The design documents in doc/graft/PLAN*.md explain why things are the way they are.

Credits and license

open_scion is MIT licensed, see LICENSE.

It started as a fork of Gitaly, GitLab's Git RPC server (MIT, Copyright GitLab Inc.), which provides the Git plumbing underneath; every upstream Gitaly RPC keeps working. The non-MIT ee/ directory of upstream Gitaly is not part of this repository. Gitaly's own README is kept in doc/UPSTREAM-GITALY.md, and third-party notices are in NOTICE.

git-ai (feder-cr/git-ai)

monitoring
Searching Database…

1.1K ·GitHub
Git-ai
What is this?openscion is an open-source, MIT-licensed reimplementation of Scion, the server-centric version control system Anthropic built internally for coding agents but never released publicly.
Is this a new version control system, or does it still use Git underneath?It runs normal Git repositories underneath, but moves history lookups, landing and conflict resolution to a server instead of doing them client-side the way classic Git hosting does.
How do I get a server running?Adapt the example config at examples/graft/config.toml and start the server with build/bin/gitaly serve config.toml; building compiles a bundled Git via Meson and Ninja.
What do I need installed to build and run it?Linux or macOS, Go 1.26, a C toolchain, Meson and Ninja to build; add a database (SQLite or PostgreSQL) plus object storage (file, S3, GCS or Azure) if you want the full storage core instead of shadow mode.
Is this production-ready?It's version 0.1.0, the first public release: the core features are implemented and tested, but interfaces may still change before 1.0, and known gaps like garbage collection of packs are tracked in LIMITATIONS.md.
Does it send my code to an AI provider to work?No. The server itself never calls a language model; conflict resolution is optional and can use any LLM provider, a deterministic tool, or none at all, through a vendor-neutral protocol.
What is 'Graft' inside the code?Graft is the internal name for openscion's extensions over Gitaly: the [graft] config section, the graft CLI, and the internal/graft code that implements the storage core and landing logic.
What happens when two agents land conflicting changes at the same time?A conflicting land is resolved by a resolver of your choice (LLM, deterministic tool, or none), and concurrent lands on one branch get batched into a single reference update instead of going through a merge queue.
How does it catch a change that breaks the build after landing?graft-verify tests the current tip, bisects any failure, and automatically reverts the change that broke it.
What is openscion actually built on top of?It started as a fork of Gitaly, GitLab's MIT-licensed Git RPC server, which still provides the underlying Git plumbing — every upstream Gitaly RPC keeps working.
What are similar projects?agentsview, seaweedfs, walgit, juicefs, hydradb, celld, durable-git, go-micro
Which topics is it in?object-storage, fuzzing, s3, version-control, slack, coding-agents, golang, distributed-systems, git, sqlite, testing, postgresql
Creator
feder-cr
Size
14.6 MB
Stars
1.1K
Updated
CommitOct 16Releasev0.1.0Oct 15
Age
2d
Commits · 90 Days