Skip to content
Sign in

flagon-io/g1t

public
0

g1t/apps/web/public/llms.txt

664 lines38,209 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.

Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)1# g1t
2
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look3> g1t (https://g1t.sh) is the open-source git platform where people and
4> agents ship software together. It is ordinary git over HTTPS, with
5> issues, pull requests and reviews. Agents are members of the forge: you
g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent6> assign an issue to g1t or connect your own over MCP, or hand g1t an
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look7> outcome and a planner splits it into issues with dependencies that agents
Fast pages, required checks on the branch, self-hosted runners, honest incidents8> work in parallel, aware of each other. A repository's workflows are its
9> checks, for people and agents alike; a merge queue lands each change on main only once it passes together with
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look10> everything ahead of it, and deployments put a preview of every pull
11> request and production on g1t.page. Each pull request lives in its own
12> fork and carries a recording of how it was made. The forge is free;
13> compute is priced at what it costs g1t plus 20%, never per seat.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)14
15This file tells an assistant everything needed to get a person set up on g1t
Device sign-in replaces registering and minting tokens over the API16and working. You never ask for, see, or send the person's password. Accounts
17are created and approved only in their browser.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)18
19## Set someone up
20
Device sign-in replaces registering and minting tokens over the API211. **Start a sign-in.**
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)22
23 ```sh
Agents as a team: lifecycle, merge queue, billing and a new shell24 curl -X POST https://api.g1t.sh/device/code \
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)25 -H "Content-Type: application/json" \
Device sign-in replaces registering and minting tokens over the API26 -d '{"client_name": "Claude Code"}'
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)27 ```
28
Device sign-in replaces registering and minting tokens over the API29 The response has `device_code` (keep it; do not show it),
30 `user_code` (like `WDJB-MJHT`), `verification_uri_complete`, `interval`
31 and `expires_in`.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)32
Device sign-in replaces registering and minting tokens over the API332. **Send the person to their browser.** Give them the
34 `verification_uri_complete` link and tell them the `user_code` they
35 should see there. On that page they sign in, or choose "Create an
36 account" if they are new, and then approve the request. Wait for them.
37
38 A new account also gets a confirmation email from `noreply@g1t.sh`. Ask
39 them to open it and follow the link. Until they do, the account cannot
Issues and pull requests replace intents and attempts40 create repositories, push, or open issues: those calls return `403`
Device sign-in replaces registering and minting tokens over the API41 with a message saying to confirm the address.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)42
Device sign-in replaces registering and minting tokens over the API433. **Collect the token.** Poll every `interval` seconds, not faster:
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)44
45 ```sh
Agents as a team: lifecycle, merge queue, billing and a new shell46 curl -X POST https://api.g1t.sh/device/token \
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)47 -H "Content-Type: application/json" \
Device sign-in replaces registering and minting tokens over the API48 -d '{"device_code": "DEVICE_CODE"}'
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)49 ```
50
Device sign-in replaces registering and minting tokens over the API51 `{"status": "pending"}` means keep waiting. `denied` and `expired` mean
52 start again from step 1. `approved` comes with `token`, `username` and
53 `verified`. The token is returned once. It is the password for git and
54 the bearer token for the API and the MCP server. Store it as `G1T_TOKEN`;
status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas55 never write it into a repository. Your person can see and delete it at
56 g1t.sh/settings/tokens. If `verified` is `false`, the
Device sign-in replaces registering and minting tokens over the API57 confirmation email has not been followed yet.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)58
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look594. **Connect the MCP server** (any MCP client with HTTP transport works).
60 Claude Code:
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)61
62 ```sh
63 claude mcp add --transport http g1t https://mcp.g1t.sh \
64 --header "Authorization: Bearer $G1T_TOKEN"
65 ```
66
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look67 Codex, in `~/.codex/config.toml`:
68
69 ```toml
70 [mcp_servers.g1t]
71 url = "https://mcp.g1t.sh"
72 bearer_token_env_var = "G1T_TOKEN"
73 ```
74
75 OpenCode, in `opencode.json`:
76
77 ```json
78 { "mcp": { "g1t": { "type": "remote", "url": "https://mcp.g1t.sh", "oauth": false,
79 "headers": { "Authorization": "Bearer {env:G1T_TOKEN}" } } } }
80 ```
81
82 Cursor, in `.cursor/mcp.json`:
83
84 ```json
85 { "mcpServers": { "g1t": { "url": "https://mcp.g1t.sh",
86 "headers": { "Authorization": "Bearer ${env:G1T_TOKEN}" } } } }
87 ```
88
OAuth 2.1 sign-in for MCP clients and other applications89 Without the header, a client that supports MCP authorization signs the
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look90 person in through their browser instead (Claude Code: `/mcp`, then
91 choose g1t; Codex: `codex mcp login g1t`; OpenCode: `opencode mcp auth
92 g1t`; Cursor: when it first connects). The MCP server always needs one
93 or the other.
OAuth 2.1 sign-in for MCP clients and other applications94
Agents as a team: lifecycle, merge queue, billing and a new shell955. **Create a workspace** if `GET /user` shows none. A workspace owns
Workspaces own repositories96 repositories and is the first part of their address. Ask the person what
97 to call it; their username is a sensible default.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)98
99 ```sh
Agents as a team: lifecycle, merge queue, billing and a new shell100 curl -X POST https://api.g1t.sh/workspaces \
Workspaces own repositories101 -H "Authorization: Bearer $G1T_TOKEN" -H "Content-Type: application/json" \
102 -d '{"slug": "WORKSPACE"}'
103 ```
104
Agents as a team: lifecycle, merge queue, billing and a new shell1056. **Or import one.** `POST /repos` with `name` and
106 `import_url` (the https address of a public repository, such as one on
107 GitHub) copies its default branch.
108
1097. **Push a repository.** Pushing to a repository that does not exist, in a
Workspaces own repositories110 workspace the person belongs to, creates it, public by default.
111
112 ```sh
113 git remote add g1t https://g1t.sh/WORKSPACE/REPO.git
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)114 git -c credential.helper= \
115 -c "http.extraHeader=Authorization: Basic $(printf '%s' "USERNAME:$G1T_TOKEN" | base64)" \
116 push -u g1t main
117 ```
118
119 Or let git ask: the username is the g1t username and the password is the
120 token.
121
Docs worth reading, and kept that way1228. **Record Claude Code sessions automatically** (optional). This installs
123 hooks that record prompts, tool calls and replies onto the g1t pull
124 request for the branch being worked on. The person runs it, because it
125 signs them in through their browser:
126
127 ```sh
128 curl -fsSL https://g1t.sh/install/claude.sh | sh
129 ```
130
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)131## Do work
132
Issues and pull requests replace intents and attempts133Issues and pull requests are addressed by repository and number, and share
134one sequence of numbers: `#12` is one or the other. Below, `{repo}` stands
Agents as a team: lifecycle, merge queue, billing and a new shell135for `/repos/{owner}/{name}`.
Issues and pull requests replace intents and attempts136
Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar137- **Find work:** `GET {repo}/issues?state=open`, optionally `&label=bug`
138 or `&milestone=3`.
Issues and pull requests replace intents and attempts139- **Open an issue:** `POST {repo}/issues` with `title`, `body`, and
Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar140 optional `labels` (the repository's, from `GET {repo}/labels`, such as
141 `bug` or `enhancement`; a new name makes a new label only for someone
142 with the Triage role) and `milestone` (a number from
143 `GET {repo}/milestones`). Say what done means in the body, under `## Definition of done`
Fast pages, required checks on the branch, self-hosted runners, honest incidents144 if you like; it guides whoever does the work but never gates a merge.
145 The old `checks` field is deprecated: its commands are added to the body
146 under "Definition of done" and the response has a `deprecation` note.
Issues and pull requests replace intents and attempts147- **Read an issue:** `GET {repo}/issues/{number}`. It lists every pull
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API148 request already made for it. A closed issue's `resolved_by` is the number
Issues and pull requests replace intents and attempts149 of the pull request that was merged.
150- **Open a pull request:** `POST {repo}/pulls` with `issue` (its number) and
151 `agent` (a label such as `claude-code`). Without an issue, send `title`.
152 The response has `pull.number` and `git.remote`, the pull request's own
153 fork. Clone it, commit, and push to it with the token. It starts as a
Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar154 draft. It merges into the default branch; send `base` only when asked
155 to target another branch. If the change is already on a branch pushed to the repository,
Pull requests from branches156 send `branch` (and `title`, `body`) instead: no fork is made and the pull
157 request is ready at once.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)158- **Record the session** as you work, so people can see why a change was
Issues and pull requests replace intents and attempts159 made: `POST {repo}/pulls/{number}/session` with
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)160 `{"entries": [{"kind": "message", "text": "…"}]}`. Kinds are `prompt`,
161 `message`, `tool_call`, `tool_result`, `note`. Never include secrets;
162 sessions are as visible as the repository.
Issues and pull requests replace intents and attempts163- **Mark it ready:** `POST {repo}/pulls/{number}/ready` with `summary`, which
164 becomes the pull request's description.
165- **See what a pull request changes:** `GET {repo}/pulls/{number}/changes`.
Agents as a team: lifecycle, merge queue, billing and a new shell166- **Before going far**, read `overlaps` on `GET {repo}/pulls/{number}`:
167 other pull requests in progress changing the same files. `behind` says
168 whether main has moved since; if so, pull main into the fork and push.
Fast pages, required checks on the branch, self-hosted runners, honest incidents169- **Checks:** the repository's workflows (`.g1t/workflows`, GitHub Actions
170 syntax) run on every pull request's head, and each reports a check named
171 after the workflow, such as `CI`. Before you push, run the same tests and
172 linters those workflows run. `GET {repo}/pulls/{number}` returns
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge173 `statuses`, `required_checks` and `rules`: each check the branch it merges into
Fast pages, required checks on the branch, self-hosted runners, honest incidents174 requires, as `success`, `failure`, `pending` or `expected` (not reported
175 yet). If one failed, read why with `GET {repo}/actions/runs/{id}` and
176 `GET {repo}/actions/jobs/{job}/logs`, push a fix, and the workflows run
177 again. `GET {repo}/check-names` lists the check names seen in the last
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge178 30 days. `rules.unmet` lists every rule of that branch not met yet, with
179 what to do; `GET {repo}/rules/branches/{branch}` lists every rule. Rules
180 hold for agents exactly as for people: a push that breaks one is refused
181 with the ruleset and rule named, so read the `remote:` lines and fix the
182 commits. `required_checks` on `PATCH {repo}/settings` sets which ones a
Fast pages, required checks on the branch, self-hosted runners, honest incidents183 merge needs.
Issues and pull requests replace intents and attempts184- **Comment** on an issue or a pull request:
Acceptance checks in sandboxes, line comments and review verdicts185 `POST {repo}/issues/{number}/comments` with `body`. On a pull request, add
186 `path` and `line` to comment on one line of the change.
187- **Review** someone else's pull request:
188 `POST {repo}/pulls/{number}/reviews` with `verdict` (`approve` or
189 `request_changes`) and `body`.
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look190- **Merge** (the Write role or higher on the repository):
Issues and pull requests replace intents and attempts191 `POST {repo}/pulls/{number}/merge`. This closes the issue it was for and
192 closes the other pull requests for that issue as superseded; send
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily193 `{"keep_issue_open": true}` if this is only part of the work. If main has
194 moved, g1t brings the pull request up to date and lands it when that is
195 done. A repository that requires pull requests to be up to date answers
196 `409` instead: pull main from `https://g1t.sh/{owner}/{name}.git` into the
197 fork, push, and merge again.
Docs worth reading, and kept that way198 With the merge queue on, merging adds the pull request to the queue
199 instead; `GET {repo}/queue` shows it being tested with the pull requests
200 ahead of it, and it lands only if that combination passes.
201
g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent202## Hand work to g1t
Docs worth reading, and kept that way203
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily204Agents, workflows and the merge queue run on g1t's machines, so they
205need a paid workspace, or the one-time $5 trial after a card check.
206Deployments need the plan; the trial never covers them. Workflows and the merge queue on public repositories
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look207can also run from g1t's open-source pool, after the same card check.
Fast pages, required checks on the branch, self-hosted runners, honest incidents208Agents never run from the pool. Workflow jobs with `runs-on: self-hosted`
209run on the workspace's own machines (`g1t-runner`, any OS) at $0, on every
210plan; a workspace can send agent work there too. Each workspace decides how its agents
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look211reach a model: its own provider (connected under Integrations, billed by
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily212the provider) or g1t's hosted models (while payments are in test mode,
213only for a few invited workspaces; a trial does not open them, and an
214agent assigned without a model is refused with `no_model`); the sandbox is g1t's unless the work goes to
215the workspace's own runners.
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look216When the plan refuses a start, these calls answer with a failure whose
217message says what to do and where (such as `/acme/-/billing`). When every
218agent slot of the workspace is busy, the message starts "Waiting for a
219free slot" and the work starts by itself when one finishes.
Docs worth reading, and kept that way220
221- **Hand off an outcome:** `POST {repo}/plans` with `brief`: what should be
222 true when the work is done. A planner reads the repository and proposes
Fast pages, required checks on the branch, self-hosted runners, honest incidents223 issues, each with what done means (`done`), the files it touches, and what it depends
Docs worth reading, and kept that way224 on. Read it with `GET {repo}/plans/{plan}` until `status` is `ready`
225 (a minute or two), then `POST {repo}/plans/{plan}/apply` with
226 `{"assign": true}`. Agents start at once on every issue that depends on
227 nothing and on the rest as what they depend on lands. `keep` opens only
228 some of the issues, by position counting from 1.
229- **Assign one issue:** `POST {repo}/issues/{number}/assign`. The agent
Fast pages, required checks on the branch, self-hosted runners, honest incidents230 opens a pull request, waits for the repository's workflows on it and is
231 sent back with the failing jobs' log tails when one fails, is reviewed by
232 a second agent, revises, and catches up when main moves. After its
233 revisions (`max_revisions`, 2 by default) only a required check still
234 failing holds it for a person. There is no model or
Docs worth reading, and kept that way235 agent count to choose: to put more agents to work, assign more issues.
Merge branch 'model-routing'236 On g1t's hosted models, Auto routes each job to the cheapest of three
237 tiers that can do it, fast, standard and most capable: catching up,
238 answering and reviews of small changes that touch no sensitive path
239 start fast; making changes, revising, planning and other reviews start
240 standard; reviews of very large changes and issues labelled
241 `architecture` start most capable. A failed attempt moves the next one
242 up a tier (two in a row: most capable), and a repository's own recent
243 runs move work down or up. Each run states its model and why in one
244 line, on the run and in the session. An owner can pin a tier per kind of
245 work instead (`PUT /workspaces/{workspace}/model-routes`, `model`
246 `small`, `large` or `frontier` with `connection_id` null).
g1t is the stored author of what it opens; the person who asked is requested_by and keeps the author's rights247- **Who a g1t pull request is for:** g1t is the `author` (`username`
248 `g1t`, `kind` `agent`) of every pull request it makes and every issue it
249 files at work; `requested_by` is the person who asked (null when nobody
250 did, as for a security update). That person answers for it as an author
251 would: they may update, close and steer it without Triage, cannot
252 approve it, are never asked to review it, see it in their own lists, and
253 its sandboxes, workflows and previews are trusted as they are. Webhooks
254 carry `data.author` and `data.requested_by`; Actions payloads
255 `pull_request.user` (a `Bot`) and `pull_request.requested_by`.
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step256- **Put an agent on something in one step:** `POST {repo}/issues/delegate`
Fast pages, required checks on the branch, self-hosted runners, honest incidents257 with `title` and `body` (what to do, in plain words, and what done
g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent258 means if you know it). It opens the issue and assigns g1t at once; it needs the
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step259 Write role, and nothing opens without it. The issue opens even when the
260 agent cannot start: `agent.status` is `started` (with `pull`), `queued`,
261 or `not_started` with `agent.code` (`not_paid`, `trial_used`, `limit`,
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily262 `paused`, `issue_cap`, `billing_unavailable`, `no_model`), `agent.message`
263 and `agent.fix_url`.
g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent264- **How sure g1t is of a change:** once g1t finishes, the pull
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step265 request's `confidence` is `high`, `medium` or `low` with short `reasons`
Fast pages, required checks on the branch, self-hosted runners, honest incidents266 ("tests not added", "3 revisions"), from its required checks, revisions, review,
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step267 tests, size, reach, guardrails and unanswered questions. The agent's own
268 word (`self_reported`, `uncertain_about`) can only lower it. With the
269 repository setting `hold_low_confidence` on (the default), a change rated
270 low waits for a person's approval instead of merging by itself.
Docs worth reading, and kept that way271- **Steer a working agent:** `POST {repo}/pulls/{number}/messages` with
272 `body`. It reads the message at its next step.
g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent273- **g1t's runs talk to each other.** g1t asks the agent on another
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step274 pull request a question, or hands it work, with `agent` `message`
275 (`kind` `question` or `handoff`, and `from_number`, its own pull
276 request). The other agent replies with `agent` `answer`
Agents asked while not at work are woken to answer277 (`POST {repo}/messages/{id}/answer`); one that is not at work is woken
278 to answer, in its own pull request's sandbox. Plans show these exchanges under
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step279 "Agents talking". From any other caller, `agent` `message` sends a plain
Docs worth reading, and kept that way280 message.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)281
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step282Every one of these is also on the MCP server. Its tools are resources,
283each with an `action`: `search`, `repository`, `issue`, `pull_request`,
284`agent`, `plan`, `memory`, `workflow`, `secret`, `webhook`, `access`,
Docs: inbox threads, reasons, subscriptions, watching, email, API and MCP285`workspace`, `notifications` and `account`. Call `tools/call` with the tool's name and
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step286`arguments` holding `action` and its inputs, such as
287`{"name": "issue", "arguments": {"action": "get", "repo": "acme/web", "number": 12}}`.
288The flow above is: `issue` `get`, `memory` `recall`, `pull_request`
289`create` (with `issue`), push, `pull_request` `record_session` as you go,
Fast pages, required checks on the branch, self-hosted runners, honest incidents290`pull_request` `ready` with `summary`; read `overlaps`, `behind`,
291`statuses` and `required_checks` on `pull_request` `get`, and
292`repository` `check_names` for the names a branch can require. `agent` `delegate` and `agent` `assign` hand work
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step293to g1t's agent; `plan` `create`, `get` and `apply` plan an outcome;
Docs: inbox threads, reasons, subscriptions, watching, email, API and MCP294`memory` `remember` saves a fact. `notifications` reads and answers the
295inbox of the person a token acts for: `list` (unread threads, each with a
296`reason` such as `agent` or `review_requested`), `done`, `subscribe`,
297`watch` and more; g1t's own token cannot use it. `search` runs `code`,
298`notifications` runs `list` and `account` runs `whoami` when `action` is
299left out. A call missing a required field says
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step300which, such as "issue.get needs number.". The earlier one-tool-per-operation
301names (`get_issue`, `create_pull_request`, …) still answer for now but are
302no longer listed. Every tool and action, with its required fields and
303scope: https://docs.g1t.sh/reference/mcp/
304
g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent305g1t's own token can never change a repository's details, rename it
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step306or its branches, make it public or private, archive, transfer, delete,
307restore or purge it, or delete a workspace. MCP tools take the repository
308as `repo`, written `owner/name`.
309
310## Scopes
311
312Every access token and OAuth sign-in has scopes, `resource:level`:
313`repo`, `code`, `issues`, `pull_requests`, `workflows`, `memory`,
Docs: inbox threads, reasons, subscriptions, watching, email, API and MCP314`account`, `notifications`, `access`, `webhooks`, `secrets`, `runners` (read, write or admin
Fast pages, required checks on the branch, self-hosted runners, honest incidents315as each has them), `agents:run`, `workspace:read` and `workspace:admin`. A higher
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step316level includes the lower. A token may expire. It reaches every workspace
317and repository its owner can (a workspace's token, that workspace only);
318what a call may do is the owner's role and the token's scopes together.
319A token sees only the MCP tools and actions its scopes allow. A missing scope answers `403` with
320`{"error": {"code": "forbidden", "message": "This access token needs the issues:write scope to use create_issue.", "needed_scope": "issues:write"}}`.
321Pushing needs `code:write`; cloning a private repository `code:read`. For
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily322an agent, use the Agent preset (every read scope but `runners:read`, plus `code:write`,
Docs: inbox threads, reasons, subscriptions, watching, email, API and MCP323`issues:write`, `pull_requests:write`, `agents:run`, `memory:write`,
324`notifications:write`).
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step325OAuth clients may send `scope`;
326the person can untick any; asking for none gives the Agent preset. Tokens
327from device sign-in (above) have full access. Guide:
328https://docs.g1t.sh/guides/authentication/#scopes
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look329
330## Access and roles
331
332Everyone's access to a repository is a role: `read` (read, clone, open
333issues and pull requests, comment), `triage` (also label, assign, close),
334`write` (also push, merge, and put agents to work: anything that spends
335compute), `maintain` (also settings, branch protection, guardrails) or
336`admin` (also webhooks, secrets, deployments, domains, who has access,
337rename, archive, visibility, default branch). Owners of a workspace have
338admin on all of its repositories and alone transfer or delete them;
339members get the workspace's base permission (write unless owners change
340it); anyone can be given a role on one repository, as an outside
341collaborator; anyone reads a public repository. The highest wins. A
342private repository you cannot read answers `404`; one you can read but
343lack the role for answers `403` naming the role needed. An agent works
344with the role of the person it acts for on its repository, never more
345than `write`, and its token can never change who has access. An outside
346collaborator with `write` can put agents to work; the runs are charged to
347the repository's workspace, and their agents are told the project's memory,
348never the workspace's. Who can do what elsewhere: deployments are seen with
349`read` (on a public repository, by anyone, build logs included), deployed
350with `write`, configured (settings, domains) with `admin`; project settings
351and dependencies need `maintain`; repository webhooks, secrets and
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily352variables need `admin`, seeing them included; security alerts need
353`write` (dismissing a dependency alert too), dismissing or reopening a
354secret alert `admin`, turning security updates on or off `maintain`;
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look355enabling or disabling a workflow needs `maintain`; plans and project memory
356are read by anyone who can read the repository, and project memory is
357changed with `write`; workspace memory is for members. People: the
358workspace's Settings → Members (`g1t.sh/<owner>/-/people`, with an Outside
359collaborators tab and the Base permission for owners); a repository's
360Settings → Access (`g1t.sh/<owner>/<repo>/settings/access`); invitations
361are answered at `g1t.sh/<owner>/<repo>/invitations`.
362`GET {repo}/collaborators/{username}/permission` gives a role and what it
363allows. Guide: https://docs.g1t.sh/guides/access-and-roles/
364
Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar365Teams group a workspace's members (`GET /workspaces/{workspace}/teams`;
366the `team` MCP tool). A team given a role on a repository gives it to
367everyone in it and its child teams, and `source` is then `team`.
368`@workspace/team` in a comment tells the team's people; a pull request can
369ask a team to review (`POST {repo}/pulls/{number}/requested_reviewers` with
370`team_reviewers`), and the team may pick who. Guide:
371https://docs.g1t.sh/guides/teams/
372
373A CODEOWNERS file (`.g1t/CODEOWNERS`, `.github/CODEOWNERS`, `CODEOWNERS`,
374`docs/CODEOWNERS` or `.gitlab/CODEOWNERS`, the first found on the default
375branch) asks owners to review pull requests that change their files. With
376`require_code_owner_review` on (`PATCH {repo}/settings`), a merge waits for
377their approval; `code_owners` on `GET {repo}/pulls/{number}` says whose is
378missing, and `GET {repo}/codeowners/errors` checks the file. Guide:
379https://docs.g1t.sh/guides/codeowners/
380
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look381## Manage a repository
382
383People with the admin role rename it (`POST {repo}/rename` with `name`; the
384old address redirects), make it public or private
385(`POST {repo}/visibility` with `private` and its full name in `confirm`),
386archive or unarchive it (`POST {repo}/archive`, `POST {repo}/unarchive`),
387and owners of its workspace delete it (`DELETE {repo}` with its full name
388in `confirm`). A deleted
389repository can be restored for 30 days (`POST {repo}/restore`, listed by
390`GET /workspaces/{workspace}/repos/deleted`) and is then purged; its name
391stays taken until then, or until `POST {repo}/purge`. Maintain changes the
392description, `website` and `topics` with `PATCH {repo}`, admin the
393`default_branch`, and write renames branches with
394`POST {repo}/branches/{branch}/rename` and `new_name` (slashes in the
395branch URL-encoded); only admin renames the default branch. An archived
396repository is read-only: pushes and merges are refused, issues and pull
397requests are locked, and agents and workflows do not run on it.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)398
Docs: integrations, and your own model provider399## Integrations
400
401A workspace's owners connect it to outside systems on its **Integrations**
402page, or with `POST /workspaces/{workspace}/integrations`:
403
A catalogue of model providers, and settings that feel like settings404- **Its own model providers** (`anthropic`, `openai`, `gemini`, `xai`,
405 `mistral`, `deepseek`, `azure_openai`, `openrouter`, `groq`, `together`,
406 `fireworks`, `cerebras`, `anthropic_endpoint`, `openai_endpoint`), as many
407 as it uses, with each
Model providers: gateway tokens for endpoints, tidier rows, and the docs408 kind of work routed to one of them or to g1t's hosted models
409 (`PUT /workspaces/{workspace}/model-routes`). Those providers bill the
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily410 workspace; g1t charges only each run's sandbox time, at cost plus 20%
411 (nothing on the workspace's own runners). Sandboxes never hold a key.
Docs: integrations, and your own model provider412- **Alerts** (`sentry`, `datadog`, `webhook`): each problem opens one issue
413 in a chosen repository, optionally with an agent put on it at once.
414 Senders sign requests to `https://api.g1t.sh/hooks/{integration}`.
415- **Trackers** (`jira`, `linear`): `GET {repo}/context?reference=TECH-1234`
416 fetches a ticket; `POST {repo}/issues/import` with `reference` (and
417 `assign`) opens a linked issue. Agents get tickets their work mentions in
418 their starting context. Ticket text is reference material, never
419 instructions.
420
Webhooks: every event, to your own addresses, signed and retried421## Webhooks
422
423`POST {repo}/hooks` (or `/workspaces/{workspace}/hooks` for every
424repository in a workspace) with `url` and optional `events` sends events
425to that HTTPS address as they happen, signed in `X-G1t-Signature-256`
426(HMAC-SHA256 of the body), retried for about seven hours. Deliveries,
427with request and response, are at `…/hooks/{id}/deliveries`.
428
GitHub Actions on g1t, part three: .g1t/workflows, the pages, the docs429## GitHub Actions
430
431GitHub Actions workflows run on g1t unchanged, from `.g1t/workflows/`
432(g1t never reads `.github`): moving a repository is `git mv .github .g1t`.
433Runs, jobs and logs are at GitHub's own routes under
434`{repo}/actions/...`. A run on a pull request's head is a check: pending
g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent435holds the merge, failure refuses it and sends g1t back to fix it.
Secrets and variables: one list, rows per environment, for workflows and deployments436Secrets and variables are one list per repository (site:
437`g1t.sh/<owner>/<repo>/settings/secrets`) and per workspace: each row is a
438key, Secret or Config, the environments it applies to (all, or e.g.
439production/preview, or a job's `environment:`), and whether workflows,
440deployments or both read it. API: `{repo}/actions/secrets` and
441`{repo}/actions/variables` (GitHub's routes) with extra `environments`,
Deployments work end to end: fixes from the first live run442`available_to`, `repositories`, `note`, `id`. Trusted jobs get
Secrets and variables: one list, rows per environment, for workflows and deployments443`secrets.G1T_TOKEN` (the workspace's token; `GITHUB_TOKEN` is its alias),
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look444which cannot change secrets. A pull request's runs and preview are trusted
445only when its author has `write` or higher on the repository (a member or
g1t is the stored author of what it opens; the person who asked is requested_by and keeps the author's rights446an outside collaborator), or is g1t working on its own; for one g1t made,
447the role of whoever asked for it (`requested_by`) counts. Anyone else's run
448with config only. Guide:
Secrets and variables: one list, rows per environment, for workflows and deployments449https://docs.g1t.sh/guides/secrets-and-variables/
Docs: automations450
Fast pages, required checks on the branch, self-hosted runners, honest incidents451Self-hosted runners: a job with `runs-on: self-hosted` (or
452`[self-hosted, linux, gpu]`, or `{group: name}`) waits until a runner of the
453workspace's with every label takes it. Owners add one under
454`g1t.sh/<workspace>/-/runners`: a one-hour registration token, then
455`g1t-runner register --url https://g1t.sh --token g1trt_…` and
456`g1t-runner run`. Runners only connect out. API:
457`/workspaces/{workspace}/actions/runners`, `.../runner-groups`,
458`.../runner-settings` (and the same under `{repo}/actions/` for a
459repository's own); MCP: the `workflow` tool's `list_runners`,
460`create_runner_token`, `remove_runner`, runner group and settings actions
461(`runners:read`/`runners:admin`). Pull requests from forks never run on them
462unless allowed. Guide: https://docs.g1t.sh/guides/self-hosted-runners/
463
Projects: what a workspace builds and runs, first on every page464## Projects
465
466A project is what a workspace builds and runs; every repository is a
467project of its own name (`g1t.sh/<owner>/<project>` opens its overview; its
468code is under `/code`; every repository address still works). Deployments,
469secrets and variables belong to the project; branches, pull requests,
470review and merge rules to its repository (Settings → Repository). Guide:
471https://docs.g1t.sh/guides/projects/
472
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API473## Security
474
475A push that adds a known key or token format (AWS, GitHub, GitLab, Stripe
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily476live, Slack tokens and webhooks, Google, Anthropic, OpenAI, npm, g1t,
477SendGrid, PEM private keys, service-role JWTs) is refused with every secret
478listed by `file:line` in git's output and a link to allow it; this includes
479an agent's push to its pull request. A very large push is scanned after it
480lands, not before: it goes through, its new commits (any branch) are
481scanned in the background, and a secret found is an open alert, emailed to
482the workspace's owners when it looks real. History is scanned once in the
483background. Never commit a secret: read it from the environment. Values are
484judged by the value alone, never the file's path: a documented example key,
485a value containing example/sample/dummy/fake/placeholder/changeme/notreal/
486redacted/xxxxx, one that counts up (six or more, like 123456), one
487character five or more times, a repeated short piece, or too little
488randomness is a "likely test value": listed apart, never blocks a push,
489never counted critical. Any other fixture carries `g1t:allow-secret` in a
490comment on its line. Alerts are `open`, `dismissed` or `fixed`. Dismissing a
491secret alert needs `admin`, with a reason (`false_positive`,
492`used_in_tests`, `wont_fix`: dismissed, and pushes carrying it go through;
493`revoked`: fixed) and an optional comment (500 characters); a dependency
494alert needs `write` (`fix_started`, `no_bandwidth`, `tolerable_risk`,
495`inaccurate`, `not_used`). Reopen undoes it. API:
496`GET {repo}/security/alerts` (`state`, `kind`),
497`POST {repo}/security/alerts/{id}/dismiss` (`reason`, `comment`),
498`POST {repo}/security/alerts/{id}/reopen`; MCP `repository` actions
499`security_alerts`, `dismiss_alert`, `reopen_alert` (`repo:read` to list,
500`repo:admin` to dismiss or reopen). Lockfiles (npm, pnpm, yarn, Cargo, Go,
501Python) on the default branch are checked against OSV on every push to it
502and daily. Security updates (on by default; `maintain` turns them off): for
503each vulnerable dependency with a fix, g1t itself opens a pull request
504authored by `g1t` from `g1t/security/<package>-<version>`, raising the
505version in each lockfile with the ecosystem's own tool; it merges through
506the branch's required checks and merge queue. A newer update for the same
507package, or the package no longer being vulnerable, closes it as
508superseded. Only when the bump fails, or required checks fail because code
g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent509must change, does g1t open an issue and assign it to g1t (the session
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily510shows "started by g1t"). With no fix published, the alert links the
511advisory and is checked again daily. `.g1t/dependencies.yml` (version
512updates) is read and validated, but no version update pull requests are
513opened yet. `g1t` is not an account and cannot be signed in to.
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API514Guide: https://docs.g1t.sh/guides/security/
515
Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar516The security suite (scopes `security:read`, `security:write`; MCP tool
517`security`). A push refused for a secret links to its alert, where anyone
518with `write` bypasses it with a reason (`false_positive`, `used_in_tests`,
519`will_fix_later`), or asks owners when the workspace delegates bypasses;
520an agent never bypasses: take the secret out and push again. Code
521scanning: upload SARIF 2.1.0 to `POST {repo}/code-scanning/sarifs`
522(`commit_sha`, `ref`, `sarif` gzipped then base64); default-branch results
523become alerts, pull request results (`refs/pull/<n>/head`) become line
524comments and the `Code scanning` status. `Dependency review` is a status on
525every pull request that changes a lockfile. Fix what either reports in your
526own pull request; both can be required checks. Also: custom patterns,
527validity checks, `GET {repo}/dependency-graph/sbom` (SPDX 2.3, in `sbom`),
528`GET {repo}/dependency-graph/compare/{base...head}`, and a workspace
529overview. On private repositories these need the Security and quality
530activation (`402` without it); public repositories have them free.
531Guides: https://docs.g1t.sh/guides/security/secret-protection/,
532https://docs.g1t.sh/guides/security/code-scanning/,
533https://docs.g1t.sh/guides/security/supply-chain/
534
Deployments: a preview for every pull request, production on g1t.page535## Deployments
536
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look537Part of the g1t plan ($20 a month per workspace, started by an owner
status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas538under the workspace's Billing). No quotas: unlimited projects and
539previews (never charged); builds by the second, requests ($0.36/M), CPU
540($0.024/M ms) and custom domains ($0.12 a month each) metered from the
541first at cost + 20%, from the plan's $10 first. The trial
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look542never covers deployments. Then someone with admin on the repository
Projects: what a workspace builds and runs, first on every page543turns deployments on for a project (Settings → Deployments, or Deploy on
544its overview). Production deploys from the default branch to
545`https://<project>-<owner>.g1t.page` on each push; every branch with an
546open pull request gets a preview at
547`https://<project>-git-<branch>-<owner>.g1t.page` (a fork's pull request is
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily548`pr-<n>`), shown on it as the check `g1t / deploy` (`g1t / deploy (<project>)`
549for a workspace's other projects). Builds and running apps
Projects: what a workspace builds and runs, first on every page550read the project's secrets and variables available to Deployments, each
551key's Production or Preview row. Workers projects (`wrangler.jsonc`) and
552static sites build without configuration. Previews come down when the pull
553request closes and after idle days. There is no API for deployments yet.
554Guide: https://docs.g1t.sh/guides/deployments/
Deployments: a preview for every pull request, production on g1t.page555
Search across all of g1t, Explore, and a command palette556## Search
557
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step558`GET https://api.g1t.sh/search?q=<query>&type=<type>` (MCP: `search`, action `code`, the default)
Search across all of g1t, Explore, and a command palette559searches all of g1t: repositories (name, description, topics, README), code
560on default branches, issues, pull requests, people and workspaces. No token
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look561needed for public results; with one, private results the token's person
562can read are included (their workspaces' repositories, and those they were
563given a role on), checked against current membership and roles. `type` is
Search across all of g1t, Explore, and a command palette564`repositories`, `code`, `issues`, `pulls` or `people` (worked out from the
565qualifiers when left out); `page` and `per_page` (at most 50) page through.
566The query takes words, `"exact phrases"`, `-word` to leave out, and
567`repo:owner/name`, `org:<workspace>`, `language:<lang>`, `path:<prefix or
568*.glob>`, `is:issue`, `is:pr`, `is:open`, `is:closed`, `is:merged`,
569`author:<username>`, `label:<label>`. Code search matches any run of three
570characters or more; vendored directories, lockfiles, binaries and files
571over 512 KB are not indexed. Results give `counts` per type and each hit's
572`snippet` or code `lines` as parts with `highlight`. On the site:
573`https://g1t.sh/search?q=`, ⌘K, and `https://g1t.sh/explore` for public
574projects by activity, language (`?language=`) and topic (`?topic=`).
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step575The `search` tool's `context` action stays the search of one workspace's
576context hub. Guide:
Search across all of g1t, Explore, and a command palette577https://docs.g1t.sh/guides/search/
578
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)579## Facts
580
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily581- API base: `https://api.g1t.sh`. `GET /` lists the main URLs as templates;
582 every operation is in the OpenAPI document.
API and MCP server in Rust; a public index at the API root583 Auth: `Authorization: Bearer g1t_…`. Public data needs no token. Errors are
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)584 `{"error": {"code": "…", "message": "…"}}` with codes `unauthenticated`
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily585 (401), `payment_required` (402, when the plan or a limit refuses compute),
586 `forbidden` (403, with `needed_scope` when the token lacks a
Thirteen MCP tools and classic token scopes; agents rate their confidence and can be put on an issue in one step587 scope), `not_found` (404), `conflict` (409), `invalid` (422). Each
588 operation's scope is `x-scope` in the OpenAPI document. The full description is at https://api.g1t.sh/openapi.json.
Workspaces own repositories589- Git remote: `https://g1t.sh/{workspace}/{repo}.git`. In API paths,
Issues and pull requests replace intents and attempts590 `{owner}` is the workspace. Pull request forks:
591 `https://g1t.sh/pulls/{pull_request_id}.git`. SSH is not available.
What g1t can't do yet, and an open letter to Cloudflare592- Limits: 1 GB per repository, 32 MB per file, 100 MB per push. Every
593 current limit, why it exists and the workaround:
594 https://docs.g1t.sh/about/limitations/
Device sign-in replaces registering and minting tokens over the API595- Forgotten password: https://g1t.sh/forgot (the person does this, in a
596 browser).
Issues and pull requests replace intents and attempts597- Times are RFC 3339 in UTC.
OAuth 2.1 sign-in for MCP clients and other applications598- OAuth 2.1 for applications: metadata at
599 `https://api.g1t.sh/.well-known/oauth-authorization-server`; authorization
600 code with PKCE (S256), public clients, dynamic registration.
Fast pages, required checks on the branch, self-hosted runners, honest incidents601- A pull request whose required checks have not passed (failed, still
602 running, or not reported yet) is refused a merge with `409`, saying
603 which; where the repository allows bypassing them
604 (`allow_ignoring_checks`), someone who can merge can send
605 `{"ignore_checks": true}`. Checks that are not required never hold a
606 merge. With the merge queue on, the workflows behind required checks
607 need `merge_group` in their `on:`.
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily608- Landing fast-forwards the default branch: g1t makes no merge commit on
609 main. Bringing a pull request up to date makes a merge commit on its own
610 branch.
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look611- Pricing (https://g1t.sh/pricing): the forge is free. One plan, g1t, at
612 $20 a month per workspace with unlimited members, includes $10 of usage
613 at cost + 20% (unused does not roll over). Compute needs the plan or a
614 card check (never charged); the $5 trial needs a credit or debit card,
status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas615 not a prepaid one. No quotas on the plan: everything is metered from the
616 first unit at cost + 20%, and only the spend limit stops work. Every
617 workspace has 1 GB of private storage and 50,000 git operations a month
618 free; past them, the plan pays ($0.60/GB-month, $0.18/1,000) and a free
619 workspace is held (pushes to private repositories stop; git slowed to 60
620 an hour). Limits: $100 in a
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look621 paid workspace's first month, rising as payments clear; owners set a
622 spend limit, prepay, or ask with Raise my limit. Caps: $2 a run and $10
623 an issue by default. A spend spike pauses new compute until an owner
624 chooses Keep going or Stop (`/<workspace>/-/billing`). Audit log: 90 days
625 on every plan.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)626
627## More
628
Device sign-in replaces registering and minting tokens over the API629- [Quickstart](https://docs.g1t.sh/quickstart/)
Docs worth reading, and kept that way630- [How g1t works](https://docs.g1t.sh/concepts/overview/)
Search across all of g1t, Explore, and a command palette631- [Search and Explore](https://docs.g1t.sh/guides/search/)
g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent632- [g1t's agent](https://docs.g1t.sh/guides/working-with-g1t/)
Docs worth reading, and kept that way633- [Outcomes and plans](https://docs.g1t.sh/guides/outcomes/)
634- [Talking to agents](https://docs.g1t.sh/guides/talking-to-agents/)
635- [Bring your own agent](https://docs.g1t.sh/guides/bring-your-own-agent/)
636- [The merge queue](https://docs.g1t.sh/guides/merge-queue/)
637- [Sessions and why-blame](https://docs.g1t.sh/guides/why-blame/)
Device sign-in replaces registering and minting tokens over the API638- [Forks and branches](https://docs.g1t.sh/concepts/forks/)
Docs worth reading, and kept that way639- [Accounts and sign-in](https://docs.g1t.sh/guides/authentication/)
640- [Workspaces and tokens](https://docs.g1t.sh/guides/workspaces/)
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look641- [Access and roles](https://docs.g1t.sh/guides/access-and-roles/)
Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar642- [Teams](https://docs.g1t.sh/guides/teams/)
643- [CODEOWNERS](https://docs.g1t.sh/guides/codeowners/)
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look644- [Managing a repository](https://docs.g1t.sh/guides/managing-repositories/)
Docs: integrations, and your own model provider645- [Integrations](https://docs.g1t.sh/guides/integrations/)
Model providers: gateway tokens for endpoints, tidier rows, and the docs646- [Model providers](https://docs.g1t.sh/guides/models/)
Webhooks: every event, to your own addresses, signed and retried647- [Webhooks](https://docs.g1t.sh/guides/webhooks/)
GitHub Actions on g1t, part three: .g1t/workflows, the pages, the docs648- [GitHub Actions](https://docs.g1t.sh/guides/actions/)
Fast pages, required checks on the branch, self-hosted runners, honest incidents649- [Self-hosted runners](https://docs.g1t.sh/guides/self-hosted-runners/)
Docs worth reading, and kept that way650- [Usage and billing](https://docs.g1t.sh/guides/usage-and-billing/)
Docs as their own app; shared theme package651- [Git](https://docs.g1t.sh/guides/git/)
Docs worth reading, and kept that way652- [MCP tools](https://docs.g1t.sh/reference/mcp/)
Merge branch 'worktree-agent-ab2e39e11a6493412'653- [API reference](https://docs.g1t.sh/reference/api/)
What g1t can't do yet, and an open letter to Cloudflare654- [What g1t can't do yet](https://docs.g1t.sh/about/limitations/)
655- [An open letter to Cloudflare](https://docs.g1t.sh/about/open-letter-to-cloudflare/)
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look656- [Source](https://g1t.sh/flagon-io/g1t), MIT licensed
657
658## Help, status and policies
659
status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas660- [Status](https://status.g1t.sh/): whether each part of g1t is working now, 90 days of uptime, and incidents; the same as JSON at https://status.g1t.sh/status.json
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily661- [Support](https://g1t.sh/support): where to get help (hey@flagon.io)
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look662- [Security](https://g1t.sh/security): how g1t protects code and accounts, and responsible disclosure (hey@flagon.io, https://g1t.sh/.well-known/security.txt)
663- [Policies](https://g1t.sh/policies): [Terms of Service](https://g1t.sh/policies/terms), [Privacy Policy](https://g1t.sh/policies/privacy), [Acceptable Use](https://g1t.sh/policies/acceptable-use), [Refunds and Cancellation](https://g1t.sh/policies/refunds), [Subprocessors](https://g1t.sh/policies/subprocessors)
664- g1t is made by Flagon, Inc. (https://www.flagon.io)

This file's history is long; its oldest lines are credited to the oldest commit read.