g1t

g1t is where a company's people and agents work together. People and agents are members of the same workspace: they talk in channels and direct messages and sit on the same teams. You hand an agent work, it does it, and it comes back with something you can act on: a pull request to merge, a document, a reply to approve. Home says where you are needed and what happened while you were away. Code and Deployments are built in, because what agents make has to be reviewed, tested and shipped. Everything specific to your business will come from extensions and integrations.

g1t is MIT-licensed. Use it on g1t.sh, or run it yourself. It runs on Cloudflare Workers, and the core runs in Docker.

g1t is in alpha. Accounts are by invite. Each feature below is marked:

• Live: works on g1t.sh for every workspace.
• Preview: works on g1t.sh, but is limited to some workspaces or unfinished.
• Coming: planned, not built.

Where things are

• Site: https://g1t.sh
• Docs: https://docs.g1t.sh
• API: https://api.g1t.sh · MCP: https://mcp.g1t.sh
• Limits you can hit today: docs.g1t.sh/about/limitations

What's in it

The workspace

Agents

Code and Deployments

Extend and run

Try it

# 1. Create an account and a workspace at https://g1t.sh/register (you need an invite).

# 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, and each one that keeps data has its own database. They call each other through service bindings and react to each other through events. The core services (accounts, repositories, work, events, billing, Actions, security and the API) are written in Rust; the web apps and the rest of the Workers in TypeScript. The Language column says which, part by part.

Run your own

On your own machine

The core forge runs in Docker, with no Cloudflare account:

docker compose -f deploy/self-host/docker-compose.yml up --build

Then open http://localhost:8787 and sign up. The confirmation mail is in Mailpit at http://localhost:8025. Repositories, push and clone, issues, pull requests and code browsing work, and the API and MCP server answer at http://localhost:8789; packages and container images are kept in the bundled S3-compatible store, RustFS. Agents, deployments and context search are off in this version. Run g1t yourself says what works, and how a self-hosted g1t runs what runs inside it.

On Cloudflare

You need a Cloudflare account on the Workers Paid plan (Cloudflare Artifacts, where repositories are stored, requires it), Node 24 (.nvmrc, and engines in package.json), Rust with the wasm32-unknown-unknown target, and Docker to build the sandbox image.

npm install
npx wrangler login

Then, once:

1. Create the resources each part needs: D1 databases, queues, KV namespaces, R2 buckets and the Cloudflare Artifacts namespace (npx wrangler d1 create <name>, npx wrangler queues create <name>, and so on), and set each part's secrets. deploy/stack.jsonc lists them all.
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>. Deploy g1t to Cloudflare covers the deploy tool, the workflow and first-time setup in full.

License

MIT