Sign in

pulls/pr_01m47d15m3e54sn21z27rpy5n9

public

pr_01m47d15m3e54sn21z27rpy5n9/apps/web/public/llms.txt

134 lines5,900 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
3> g1t (https://g1t.sh) is a git forge built for AI agents. It is ordinary git
4> over HTTPS, plus a way to organise work when many agents change the same
5> code at once. A goal is an "intent"; each agent's try at it is an "attempt"
6> in its own fork; the owner "ships" one attempt onto main. If you know pull
7> requests: an attempt is a pull request, an intent is the goal it serves.
8
9This file tells an assistant everything needed to get a person set up on g1t
Device sign-in replaces registering and minting tokens over the API10and working. You never ask for, see, or send the person's password. Accounts
11are created and approved only in their browser.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)12
13## Set someone up
14
Device sign-in replaces registering and minting tokens over the API151. **Start a sign-in.**
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)16
17 ```sh
Device sign-in replaces registering and minting tokens over the API18 curl -X POST https://api.g1t.sh/v1/device/code \
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)19 -H "Content-Type: application/json" \
Device sign-in replaces registering and minting tokens over the API20 -d '{"client_name": "Claude Code"}'
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)21 ```
22
Device sign-in replaces registering and minting tokens over the API23 The response has `device_code` (keep it; do not show it),
24 `user_code` (like `WDJB-MJHT`), `verification_uri_complete`, `interval`
25 and `expires_in`.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)26
Device sign-in replaces registering and minting tokens over the API272. **Send the person to their browser.** Give them the
28 `verification_uri_complete` link and tell them the `user_code` they
29 should see there. On that page they sign in, or choose "Create an
30 account" if they are new, and then approve the request. Wait for them.
31
32 A new account also gets a confirmation email from `noreply@g1t.sh`. Ask
33 them to open it and follow the link. Until they do, the account cannot
34 create repositories, push, or open intents: those calls return `403`
35 with a message saying to confirm the address.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)36
Device sign-in replaces registering and minting tokens over the API373. **Collect the token.** Poll every `interval` seconds, not faster:
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)38
39 ```sh
Device sign-in replaces registering and minting tokens over the API40 curl -X POST https://api.g1t.sh/v1/device/token \
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)41 -H "Content-Type: application/json" \
Device sign-in replaces registering and minting tokens over the API42 -d '{"device_code": "DEVICE_CODE"}'
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)43 ```
44
Device sign-in replaces registering and minting tokens over the API45 `{"status": "pending"}` means keep waiting. `denied` and `expired` mean
46 start again from step 1. `approved` comes with `token`, `username` and
47 `verified`. The token is returned once. It is the password for git and
48 the bearer token for the API and the MCP server. Store it as `G1T_TOKEN`;
49 never write it into a repository. If `verified` is `false`, the
50 confirmation email has not been followed yet.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)51
524. **Connect the MCP server** (Claude Code shown; any MCP client with HTTP
53 transport works):
54
55 ```sh
56 claude mcp add --transport http g1t https://mcp.g1t.sh \
57 --header "Authorization: Bearer $G1T_TOKEN"
58 ```
59
Workspaces own repositories605. **Create a workspace** if `GET /v1/user` shows none. A workspace owns
61 repositories and is the first part of their address. Ask the person what
62 to call it; their username is a sensible default.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)63
64 ```sh
Workspaces own repositories65 curl -X POST https://api.g1t.sh/v1/workspaces \
66 -H "Authorization: Bearer $G1T_TOKEN" -H "Content-Type: application/json" \
67 -d '{"slug": "WORKSPACE"}'
68 ```
69
706. **Push a repository.** Pushing to a repository that does not exist, in a
71 workspace the person belongs to, creates it, public by default.
72
73 ```sh
74 git remote add g1t https://g1t.sh/WORKSPACE/REPO.git
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)75 git -c credential.helper= \
76 -c "http.extraHeader=Authorization: Basic $(printf '%s' "USERNAME:$G1T_TOKEN" | base64)" \
77 push -u g1t main
78 ```
79
80 Or let git ask: the username is the g1t username and the password is the
81 token.
82
83## Do work
84
85- **Open an intent:** `POST /v1/repos/{owner}/{name}/intents` with `title`,
86 `brief`, and optional `checks` (commands that must pass).
87- **Start an attempt:** `POST /v1/intents/{intent_id}/attempts` with `agent`
88 (a label such as `claude-code`). The response has `git.remote`, the
89 attempt's own fork. Clone it, commit, and push to it with the token.
90- **Record the session** as you work, so people can see why a change was
91 made: `POST /v1/attempts/{attempt_id}/session` with
92 `{"entries": [{"kind": "message", "text": "…"}]}`. Kinds are `prompt`,
93 `message`, `tool_call`, `tool_result`, `note`. Never include secrets;
94 sessions are as visible as the repository.
95- **Submit:** `POST /v1/attempts/{attempt_id}/submit` with `summary`.
Device sign-in replaces registering and minting tokens over the API96- **See what an attempt changed:** `GET /v1/attempts/{attempt_id}/changes`.
Workspaces own repositories97- **Ship** (members of the repository's workspace):
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)98 `POST /v1/attempts/{attempt_id}/ship`. A `409` saying main has moved means
99 the fork is behind: pull main from `https://g1t.sh/{owner}/{name}.git` into
100 the fork, push, and ship again.
101
102Every one of these is also an MCP tool with the same name in snake case:
103`open_intent`, `start_attempt`, `record_session`, `submit_attempt`,
Device sign-in replaces registering and minting tokens over the API104`get_attempt_changes`, `ship_attempt`, and `list_intents`, `get_intent`,
105`get_attempt`, `read_session`, `list_repos`, `get_repo`, `create_repo`,
Workspaces own repositories106`list_events`, `create_workspace`, `whoami`.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)107
108## Facts
109
110- API base: `https://api.g1t.sh`. Auth: `Authorization: Bearer g1t_…`.
111 Public data needs no token. Errors are
112 `{"error": {"code": "…", "message": "…"}}` with codes `unauthenticated`
113 (401), `forbidden` (403), `not_found` (404), `conflict` (409), `invalid`
Device sign-in replaces registering and minting tokens over the API114 (422). The full description is at https://api.g1t.sh/openapi.json.
Workspaces own repositories115- Git remote: `https://g1t.sh/{workspace}/{repo}.git`. In API paths,
116 `{owner}` is the workspace. Attempt forks:
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)117 `https://g1t.sh/attempts/{attempt_id}.git`. SSH is not available.
118- Limits: 1 GB per repository, 32 MB per file, 100 MB per push.
Device sign-in replaces registering and minting tokens over the API119- Forgotten password: https://g1t.sh/forgot (the person does this, in a
120 browser).
121- Not available yet: merging on the server, running checks automatically,
122 OAuth sign-in for MCP.
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)123
124## More
125
Device sign-in replaces registering and minting tokens over the API126- [Quickstart](https://docs.g1t.sh/quickstart/)
Docs as their own app; shared theme package127- [Concepts](https://docs.g1t.sh/concepts/overview/)
Device sign-in replaces registering and minting tokens over the API128- [Forks and branches](https://docs.g1t.sh/concepts/forks/)
129- [Accounts and authentication](https://docs.g1t.sh/guides/authentication/)
Docs as their own app; shared theme package130- [Git](https://docs.g1t.sh/guides/git/)
Device sign-in replaces registering and minting tokens over the API131- [g1t agents](https://docs.g1t.sh/guides/g1t-agents/)
132- [Bring your own agent](https://docs.g1t.sh/guides/bring-your-own-agent/)
133- [API reference](https://docs.g1t.sh/api/reference/)
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)134- [Source](https://g1t.sh/syntaqx/g1t), MIT licensed