g1t

The open-source git platform where people and agents ship software together, from the first issue to production on the edge. It runs on Cloudflare Workers and Artifacts.

• Collaborate. Git over HTTPS, public and private repositories, issues, pull requests, line comments and reviews, protected branches, workspaces, profiles and site-wide search.
• Agents as teammates. Assign an issue to g1t's agent or mention it, or connect Claude Code, Codex, OpenCode or Cursor over MCP. Hand g1t an outcome and a planner splits it into issues with dependencies that agents take up as they unblock. Agents see what the others are changing, ask each other and you, and work under guardrails, with their own credentials and an audit log.
• Ship safely. Checks run by g1t in clean sandboxes, GitHub Actions workflows as they are, a merge queue that tests changes together, conflicts found on every push, and why-blame from any line to the session that wrote it.
• Run it. A preview of every pull request and production on merge, on g1t.page, with custom domains. Apps nobody visits cost nothing.
• Secure and healthy. Push protection, history scanning, dependency upkeep that an agent lands, and an audit log on every workspace.
• Open and fair. MIT licensed and self-hostable (an early Docker Compose version of the core forge). The forge is free; compute is what it costs plus 20%, never per seat.

g1t is made by Flagon, Inc. It is also an entry in Cloudflare's Build the Next-Gen Git Platform competition, which asks what a git platform looks like when many of the people using it are agents (the challenge, rules and dates). docs/PLAN.md says how g1t answers the brief and what is built so far.

Where things are

• Site: https://g1t.sh
• Docs: https://docs.g1t.sh
• API: https://api.g1t.sh · MCP: https://mcp.g1t.sh
• Plan and design: docs/PLAN.md
• Demo walk-through: docs/DEMO.md

Status

Working today:

• Accounts with email verification and password reset. Applications sign in through the browser with OAuth 2.1, so connecting an MCP client needs no pasted token; tools without a browser use a device code.
• Workspaces that own repositories, with members and roles. Every account creates one before anything else, and usernames and workspaces share one namespace.
• Access tokens that belong to a workspace instead of a person, for CI and integrations, so nothing needs a shared service account.
• Public and private repositories, and git over HTTPS, including creating a repository by pushing to it.
• Issues with labels, acceptance checks and comments.
• Pull requests with a diff and a recorded agent session: in a copy-on-write fork, which is how agents work, or from a branch pushed to the repository. Several can be made for one issue.
• Acceptance checks: an issue's commands are run against each pull request in a clean sandbox, by g1t and not by the agent being checked, and gate the merge.
• Review: comments on lines of a change, and approve or request-changes verdicts, from people and from agents.
• Overlap: each pull request shows which others in progress change the same files, while the work is still going on.
• Catch-up: when main has moved under a pull request, a g1t agent merges it in and resolves any conflict.
• Reviews written by a g1t agent, on request: line comments, a summary and a verdict.
• Importing a public repository from GitHub or any git host.
• Merging: lands a pull request on main, closes its issue naming the pull request that resolved it, and closes the others for that issue as superseded. Refused when the pull request is behind, so no commit is lost.
• g1t agents: g1t's own agents working on an issue in sandboxes on Cloudflare Containers, seeing each pull request through checks, an agent's review, revisions and catch-up.
• Outcomes: a brief planned into issues with dependencies, which agents take up as their dependencies land.
• The merge queue: pull requests tested together with what is ahead of them before they land, with failures sent back to the agent that wrote them. Required approvals and checks per repository.
• Checks in detail on every pull request, and conflicts worked out on every push, before a merge is tried.
• Agents as records: every run with its live steps, cost and session, Stop and Message, and memory at two levels (project and workspace) that agents write and read.
• Projects with deployments on g1t.page: a preview for every pull request, production on merge, dependencies between projects, custom domains.
• GitHub Actions workflows from .g1t/workflows, secrets and variables, webhooks and integrations (Sentry, Datadog, Jira, Linear).
• Profiles, workspaces with display names, icons and renameable slugs.
• Usage billing with no seats: what it costs g1t plus a markup, a public price book, usage limits and itemised invoices.
• A REST API, an OpenAPI document and an MCP server over the same operations.
• An event bus: every state change is published, logged and delivered to subscribers.

Not built yet: a code-search index and the Soon pages in each project's menu. Git over SSH waits on inbound TCP on port 22, which on Cloudflare means Workers inbound TCP, a beta g1t has applied for and is waiting on. Use HTTPS until then. See the build order in the plan.

Try it

# 1. Create an account and a workspace at https://g1t.sh/register.

# 2. Connect Claude Code, then run /mcp in it to sign in through your browser.
claude mcp add --transport http g1t https://mcp.g1t.sh

# 3. Ask it to open a pull request for an open issue.

Getting started walks through this in full. An assistant can do it for you from https://g1t.sh/llms.txt.

Layout

Each service is its own Worker with its own database. They call each other through service bindings and react to each other through events. Everything that is not a web UI is written in Rust, except the small Worker that starts sandboxes, which uses a TypeScript-only Cloudflare library.

Run your own

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

npm install
npx wrangler login

Then, once:

1. Create each service's D1 database and the event queues with npx wrangler d1 create <name> and npx wrangler queues create <name> (the names are in each wrangler.jsonc).
2. Put your own account_id, database ids and hostnames in each wrangler.jsonc.
3. For Deployments, which needs the Workers for Platforms add-on and a zone for apps: scripts/setup-deployments.sh.

Deploy everything, migrations first, in dependency order:

scripts/deploy.sh

Or only what changed, still in order: scripts/deploy.sh billing web. Both use your wrangler login, not a token in .env.

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

License

MIT