pr_01m47d15m3e54sn21z27rpy5n9/README.md
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 redesign | 1 | # g1t |
| 2 | ||
| Email verification, password reset, and Git for AI scale positioning | 3 | Git for AI scale: a forge for thousands of agents working on the same code at |
| 4 | once, running on Cloudflare Workers and Artifacts. | |
| API and MCP server, Rust identity service, registration, site redesign | 5 | |
| Issues and pull requests replace intents and attempts | 6 | g1t has the issues and pull requests you already know. What changes is how |
| 7 | many there are. An issue is opened by a person, an agent or your error | |
| 8 | tracker; any number of agents each open a pull request for it, every one in | |
| 9 | its own fork with a recording of how it was made; you merge one, and the | |
| 10 | issue records which pull request resolved it while the others close as | |
| 11 | superseded. | |
| API and MCP server, Rust identity service, registration, site redesign | 12 | |
| 13 | - Site: <https://g1t.sh> | |
| Issues and pull requests replace intents and attempts | 14 | - Docs: <https://docs.g1t.sh> |
| API and MCP server, Rust identity service, registration, site redesign | 15 | - API: <https://api.g1t.sh> · MCP: <https://mcp.g1t.sh> |
| 16 | - Plan and design: [docs/PLAN.md](docs/PLAN.md) | |
| 17 | ||
| 18 | ## Status | |
| 19 | ||
| 20 | Working today: | |
| 21 | ||
| OAuth 2.1 sign-in for MCP clients and other applications | 22 | - 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 attempts | 25 | - 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. | |
| Pull requests from branches | 29 | - Pull requests with a diff and a recorded agent session: in a |
| 30 | copy-on-write fork, which is how agents work, or from a branch pushed to | |
| 31 | the repository. Several can be made for one issue. | |
| Acceptance checks in sandboxes, line comments and review verdicts | 32 | - Acceptance checks: an issue's commands are run against each pull request |
| 33 | in a clean sandbox, by g1t and not by the agent being checked, and gate | |
| 34 | the merge. | |
| 35 | - Review: comments on lines of a change, and approve or request-changes | |
| 36 | verdicts, from people and from agents. | |
| Issues and pull requests replace intents and attempts | 37 | - Merging: lands a pull request on `main`, closes its issue naming the pull |
| 38 | request that resolved it, and closes the others for that issue as | |
| 39 | superseded. Refused when the pull request is behind, so no commit is lost. | |
| 40 | - g1t agents: g1t's own agents working on an issue in sandboxes on | |
| 41 | Cloudflare Containers (preview, limited accounts). | |
| 42 | - A REST API, an OpenAPI document and an MCP server over the same operations. | |
| API and MCP server, Rust identity service, registration, site redesign | 43 | - An event bus: every state change is published, logged and delivered to |
| 44 | subscribers. | |
| 45 | ||
| Acceptance checks in sandboxes, line comments and review verdicts | 46 | Not built yet: server-side merge commits, required reviews, git over SSH. See the build order in the plan. |
| API and MCP server, Rust identity service, registration, site redesign | 47 | |
| 48 | ## Try it | |
| 49 | ||
| 50 | ```sh | |
| OAuth 2.1 sign-in for MCP clients and other applications | 51 | # 1. Create an account and a workspace at https://g1t.sh/register. |
| API and MCP server, Rust identity service, registration, site redesign | 52 | |
| OAuth 2.1 sign-in for MCP clients and other applications | 53 | # 2. Connect Claude Code, then run /mcp in it to sign in through your browser. |
| 54 | claude mcp add --transport http g1t https://mcp.g1t.sh | |
| API and MCP server, Rust identity service, registration, site redesign | 55 | |
| Issues and pull requests replace intents and attempts | 56 | # 3. Ask it to open a pull request for an open issue. |
| API and MCP server, Rust identity service, registration, site redesign | 57 | ``` |
| 58 | ||
| Issues and pull requests replace intents and attempts | 59 | [Getting started](https://docs.g1t.sh/quickstart/) walks through this in |
| 60 | full. An assistant can do it for you from <https://g1t.sh/llms.txt>. | |
| API and MCP server, Rust identity service, registration, site redesign | 61 | |
| 62 | ## Layout | |
| 63 | ||
| 64 | | Path | What it is | | |
| 65 | | --- | --- | | |
| 66 | | `apps/web` | The site: server-rendered React on a Worker. Holds no data. | | |
| Issues and pull requests replace intents and attempts | 67 | | `apps/docs` | The documentation site, with the API explorer. | |
| API and MCP server in Rust; a public index at the API root | 68 | | `apps/api` | REST API and MCP server. Rust. | |
| Issues and pull requests replace intents and attempts | 69 | | `services/identity` | Accounts, workspaces, sessions, keys and tokens. Rust. | |
| 70 | | `services/repos` | Repository registry, contents, forks, diffs, landing, git over HTTPS. Rust. | | |
| Acceptance checks in sandboxes, line comments and review verdicts | 71 | | `services/work` | Issues, pull requests, reviews, check runs and sessions. Rust. | |
| Events service in Rust, with RFC 3339 times and accurate push events | 72 | | `services/events` | The event bus and its log. Rust. | |
| Acceptance checks in sandboxes, line comments and review verdicts | 73 | | `services/runner` | Starts sandboxes: for g1t agents, and for acceptance checks. | |
| 74 | | `crates/runner` | The program inside a sandbox: runs an agent, or a set of checks, and reports back. Rust. | | |
| API and MCP server, Rust identity service, registration, site redesign | 75 | | `crates/contracts` | Types and service interfaces for the Rust services. | |
| 76 | | `crates/kit` | Plumbing shared by Rust services on Workers. | | |
| 77 | | `crates/sshd` | Git over SSH, bridged to Artifacts. Not deployed yet. | | |
| 78 | | `packages/contracts` | The same interfaces for TypeScript callers. | | |
| Issues and pull requests replace intents and attempts | 79 | | `packages/theme` | Design tokens and the logo, shared by the site and the docs. | |
| API and MCP server, Rust identity service, registration, site redesign | 80 | |
| 81 | Each service is its own Worker with its own database. They call each other | |
| API and MCP server in Rust; a public index at the API root | 82 | through service bindings and react to each other through events. Everything |
| 83 | that is not a web UI is written in Rust, except the small Worker that | |
| 84 | starts sandboxes, which uses a TypeScript-only Cloudflare library. | |
| API and MCP server, Rust identity service, registration, site redesign | 85 | |
| 86 | ## Run your own | |
| 87 | ||
| 88 | You need a Cloudflare account on the Workers Paid plan (Artifacts requires | |
| Issues and pull requests replace intents and attempts | 89 | it), Node 22 or newer, Rust with the `wasm32-unknown-unknown` target, and |
| 90 | Docker to build the sandbox image. | |
| API and MCP server, Rust identity service, registration, site redesign | 91 | |
| 92 | ```sh | |
| 93 | npm install | |
| 94 | npx wrangler login | |
| 95 | ``` | |
| 96 | ||
| 97 | Then, once: | |
| 98 | ||
| 99 | 1. Create the D1 databases (`g1t`, `g1t-repos`, `g1t-work`, `g1t-events`) and | |
| 100 | the queues (`g1t-events`, `g1t-events-work`) with `wrangler d1 create` and | |
| 101 | `wrangler queues create`. | |
| 102 | 2. Put your own `account_id`, database ids and hostnames in each | |
| 103 | `wrangler.jsonc`. | |
| 104 | 3. Apply the migrations: `npx wrangler d1 migrations apply DB --remote` in | |
| 105 | each service directory. | |
| 106 | ||
| 107 | Deploy everything in dependency order: | |
| 108 | ||
| 109 | ```sh | |
| Events service in Rust, with RFC 3339 times and accurate push events | 110 | (cd services/events && npx wrangler deploy) |
| API and MCP server, Rust identity service, registration, site redesign | 111 | (cd services/identity && npx wrangler deploy) |
| Rust repos service with shipping; pull requests kept in the model | 112 | (cd services/repos && npx wrangler deploy) |
| Issues and pull requests replace intents and attempts | 113 | (cd services/work && npx wrangler deploy) |
| API and MCP server in Rust; a public index at the API root | 114 | (cd apps/api && npx wrangler deploy) |
| API and MCP server, Rust identity service, registration, site redesign | 115 | npm run deploy |
| Issues and pull requests replace intents and attempts | 116 | (cd services/runner && npx wrangler deploy) # optional: g1t agents |
| 117 | (cd apps/docs && npm run deploy) | |
| API and MCP server, Rust identity service, registration, site redesign | 118 | ``` |
| 119 | ||
| 120 | Create the first account by registering on your site, or with | |
| 121 | `node services/identity/scripts/create-user.mjs <username>`. | |
| 122 | ||
| 123 | ## License | |
| 124 | ||
| 125 | [MIT](LICENSE) |