pr_01m47d15m3e54sn21z27rpy5n9/README.md

118 lines4,759 bytesCodeBlame

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

API and MCP server, Rust identity service, registration, site redesign1# g1t
2
Email verification, password reset, and Git for AI scale positioning3Git for AI scale: a forge for thousands of agents working on the same code at
4once, running on Cloudflare Workers and Artifacts.
API and MCP server, Rust identity service, registration, site redesign5
Issues and pull requests replace intents and attempts6g1t has the issues and pull requests you already know. What changes is how
7many there are. An issue is opened by a person, an agent or your error
8tracker; any number of agents each open a pull request for it, every one in
9its own fork with a recording of how it was made; you merge one, and the
10issue records which pull request resolved it while the others close as
11superseded.
API and MCP server, Rust identity service, registration, site redesign12
13- Site: <https://g1t.sh>
Issues and pull requests replace intents and attempts14- Docs: <https://docs.g1t.sh>
API and MCP server, Rust identity service, registration, site redesign15- API: <https://api.g1t.sh> · MCP: <https://mcp.g1t.sh>
16- Plan and design: [docs/PLAN.md](docs/PLAN.md)
17
18## Status
19
20Working today:
21
OAuth 2.1 sign-in for MCP clients and other applications22- Accounts with email verification and password reset. Applications sign
23 in through the browser with OAuth 2.1, so connecting an MCP client needs
24 no pasted token; tools without a browser use a device code.
Issues and pull requests replace intents and attempts25- Workspaces that own repositories, with members and roles.
26- Public and private repositories, and git over HTTPS, including creating a
27 repository by pushing to it.
28- Issues with labels, acceptance checks and comments.
29- Pull requests, each in a copy-on-write fork, with a diff and a recorded
30 agent session. Several can be made for one issue.
31- Merging: lands a pull request on `main`, closes its issue naming the pull
32 request that resolved it, and closes the others for that issue as
33 superseded. Refused when the pull request is behind, so no commit is lost.
34- g1t agents: g1t's own agents working on an issue in sandboxes on
35 Cloudflare Containers (preview, limited accounts).
36- A REST API, an OpenAPI document and an MCP server over the same operations.
API and MCP server, Rust identity service, registration, site redesign37- An event bus: every state change is published, logged and delivered to
38 subscribers.
39
Issues and pull requests replace intents and attempts40Not built yet: pull requests from branches, server-side merge commits,
OAuth 2.1 sign-in for MCP clients and other applications41review comments on lines, running acceptance checks, git over SSH. See the build order in the plan.
API and MCP server, Rust identity service, registration, site redesign42
43## Try it
44
45```sh
OAuth 2.1 sign-in for MCP clients and other applications46# 1. Create an account and a workspace at https://g1t.sh/register.
API and MCP server, Rust identity service, registration, site redesign47
OAuth 2.1 sign-in for MCP clients and other applications48# 2. Connect Claude Code, then run /mcp in it to sign in through your browser.
49claude mcp add --transport http g1t https://mcp.g1t.sh
API and MCP server, Rust identity service, registration, site redesign50
Issues and pull requests replace intents and attempts51# 3. Ask it to open a pull request for an open issue.
API and MCP server, Rust identity service, registration, site redesign52```
53
Issues and pull requests replace intents and attempts54[Getting started](https://docs.g1t.sh/quickstart/) walks through this in
55full. An assistant can do it for you from <https://g1t.sh/llms.txt>.
API and MCP server, Rust identity service, registration, site redesign56
57## Layout
58
59| Path | What it is |
60| --- | --- |
61| `apps/web` | The site: server-rendered React on a Worker. Holds no data. |
Issues and pull requests replace intents and attempts62| `apps/docs` | The documentation site, with the API explorer. |
API and MCP server, Rust identity service, registration, site redesign63| `apps/api` | REST API and MCP server. |
Issues and pull requests replace intents and attempts64| `services/identity` | Accounts, workspaces, sessions, keys and tokens. Rust. |
65| `services/repos` | Repository registry, contents, forks, diffs, landing, git over HTTPS. Rust. |
66| `services/work` | Issues, pull requests, comments and sessions. Rust. |
API and MCP server, Rust identity service, registration, site redesign67| `services/events` | The event bus and its log. |
Issues and pull requests replace intents and attempts68| `services/runner` | Starts the sandboxes g1t agents work in. |
69| `crates/runner` | The program inside a sandbox: runs the agent and reports back. Rust. |
API and MCP server, Rust identity service, registration, site redesign70| `crates/contracts` | Types and service interfaces for the Rust services. |
71| `crates/kit` | Plumbing shared by Rust services on Workers. |
72| `crates/sshd` | Git over SSH, bridged to Artifacts. Not deployed yet. |
73| `packages/contracts` | The same interfaces for TypeScript callers. |
Issues and pull requests replace intents and attempts74| `packages/theme` | Design tokens and the logo, shared by the site and the docs. |
API and MCP server, Rust identity service, registration, site redesign75
76Each service is its own Worker with its own database. They call each other
Issues and pull requests replace intents and attempts77through service bindings and react to each other through events. Anything
78that is not a web UI is written in Rust or on its way there; the events
79service and the API are next.
API and MCP server, Rust identity service, registration, site redesign80
81## Run your own
82
83You need a Cloudflare account on the Workers Paid plan (Artifacts requires
Issues and pull requests replace intents and attempts84it), Node 22 or newer, Rust with the `wasm32-unknown-unknown` target, and
85Docker to build the sandbox image.
API and MCP server, Rust identity service, registration, site redesign86
87```sh
88npm install
89npx wrangler login
90```
91
92Then, once:
93
941. Create the D1 databases (`g1t`, `g1t-repos`, `g1t-work`, `g1t-events`) and
95 the queues (`g1t-events`, `g1t-events-work`) with `wrangler d1 create` and
96 `wrangler queues create`.
972. Put your own `account_id`, database ids and hostnames in each
98 `wrangler.jsonc`.
993. Apply the migrations: `npx wrangler d1 migrations apply DB --remote` in
100 each service directory.
101
102Deploy everything in dependency order:
103
104```sh
105(cd services/identity && npx wrangler deploy)
Rust repos service with shipping; pull requests kept in the model106(cd services/repos && npx wrangler deploy)
Issues and pull requests replace intents and attempts107(cd services/work && npx wrangler deploy)
API and MCP server, Rust identity service, registration, site redesign108npm run deploy
Issues and pull requests replace intents and attempts109(cd services/runner && npx wrangler deploy) # optional: g1t agents
110(cd apps/docs && npm run deploy)
API and MCP server, Rust identity service, registration, site redesign111```
112
113Create the first account by registering on your site, or with
114`node services/identity/scripts/create-user.mjs <username>`.
115
116## License
117
118[MIT](LICENSE)