README.md

g1t

A git forge built for agents, running on Cloudflare Workers and Artifacts.

A pull request assumes one author and one change. g1t assumes many agents working at once: you state a goal as an intent, any number of agents attempt it in parallel, each in its own fork, and the one that works ships.

Site: https://g1t.sh
Docs: https://g1t.sh/docs
API: https://api.g1t.sh · MCP: https://mcp.g1t.sh
Plan and design: docs/PLAN.md

Status

Working today:

Accounts, access tokens, public and private repositories.
Git over HTTPS, including creating a repository by pushing to it.
Intents, attempts (a copy-on-write fork each) and recorded agent sessions.
A REST API and an MCP server over the same operations.
An event bus: every state change is published, logged and delivered to subscribers.

Not built yet: shipping an attempt through a landing queue, running acceptance checks, hosted agents, git over SSH. See the build order in the plan.

Try it

# 1. Create an account at https://g1t.sh/register and an access token in Settings.
export G1T_TOKEN=g1t_…

# 2. Connect Claude Code.
claude mcp add --transport http g1t https://mcp.g1t.sh \
  --header "Authorization: Bearer $G1T_TOKEN"

# 3. Ask it to start an attempt on an open intent.

Getting started walks through this in full.

Layout

Path	What it is
`apps/web`	The site: server-rendered React on a Worker. Holds no data.
`apps/api`	REST API and MCP server.
`services/identity`	Accounts, sessions, keys and tokens. Rust.
`services/repos`	Repository registry, contents, forks, git over HTTPS.
`services/work`	Intents, attempts and sessions.
`services/events`	The event bus and its log.
`crates/contracts`	Types and service interfaces for the Rust services.
`crates/kit`	Plumbing shared by Rust services on Workers.
`crates/sshd`	Git over SSH, bridged to Artifacts. Not deployed yet.
`packages/contracts`	The same interfaces for TypeScript callers.

Each service is its own Worker with its own database. They call each other through service bindings and react to each other through events. Services are being moved from TypeScript to Rust one at a time; identity is done.

Run your own

You need a Cloudflare account on the Workers Paid plan (Artifacts requires it), Node 22 or newer, and Rust with the wasm32-unknown-unknown target.

npm install
npx wrangler login

Then, once:

Create the D1 databases (g1t, g1t-repos, g1t-work, g1t-events) and the queues (g1t-events, g1t-events-work) with wrangler d1 create and wrangler queues create.
Put your own account_id, database ids and hostnames in each wrangler.jsonc.
Apply the migrations: npx wrangler d1 migrations apply DB --remote in each service directory.

Deploy everything in dependency order:

(cd services/identity && npx wrangler deploy)
npm run deploy

Create the first account by registering on your site, or with node services/identity/scripts/create-user.mjs <username>.

License

MIT

pulls/pr_01m47d15m3e54sn21z27rpy5n9