# gitring

> Source control for coding agents. Before it writes, an agent declares an intent to gitring: its goal, its plan, and the files and functions it will change. gitring settles plans that conflict by written rules, checks each push against its plan, and asks a person only about the rest. An agent never approves anything: every approval of a plan or a merge is a person's, in the web app.

Agents connect over MCP at https://api.gitring.tech/mcp (Streamable HTTP). The program adds that address and the person approves it in their own browser (OAuth), and can revoke it in Settings. The web app is https://app.gitring.tech; the site and these docs are https://gitring.tech.

When you help a person with gitring:

- To connect yourself, follow the setup prompt below. Add the address, then wait while the person approves.
- Never ask the person for a gitring token, and never write one into a file, a command or a chat. If a program can only connect with a token, say so and point the person to https://gitring.tech/docs/agents/ ; they set it up themselves.
- Approvals, consent pages and decisions are the person's, in their own browser. Do not open or click them for the person.
- Once connected, follow the working rules gitring's server sends you, and start each task with gitring_brief.
- Changes to gitring are written first under "What's new" below.

The setup prompt, for any program that can add a remote MCP server:

    I want to connect you to gitring (https://gitring.tech), a coordination server where coding agents say what they will change before they write. Please:
    1. Read https://gitring.tech/llms.txt and https://gitring.tech/docs/agents.md.
    2. Add gitring as a remote MCP server named gitring, with the address https://api.gitring.tech/mcp, the way your program adds one; the guide lists the steps for many programs. Use its sign-in (OAuth) if it has one: a page opens in my browser, and I approve it there myself.
    3. Do not ask me for a token, do not write a token into any file or command, and do not install anything. If your program can only connect with a token in a header, stop and tell me; the guide says how I set that up myself.
    4. Once I have approved, call gitring_projects and tell me which projects you see.
    5. Tell me whether you can run git where you work. If you can, point me to the guide's section on pushing, since pushing needs one more step that I do.
    From then on, follow the working rules gitring's server sends you. Never approve anything in gitring: approvals are mine, in the web app.

The app's pages, to point a person to the right place (https://app.gitring.tech followed by the path):

- /sign-up: create an account with GitHub or Google; a new account starts on Team free for 14 days
- /sign-in: sign in the way the account was made (GitHub and Google are separate accounts unless the other way was added in Settings first)
- /start: the first run: import a repository, then connect an agent
- /inbox: everything that waits for the person: plans to approve, merges to approve, overlaps the rules left open
- /projects: the person's projects
- /projects/new: a new project: from GitHub, a git address, files, or empty
- /p/<project>: a project's Home: what is happening now and what waits for the person
- /p/<project>/work: every intent of the project and where it stands
- /p/<project>/overlaps: the intents whose plans share files or functions, and how each pair was settled
- /p/<project>/code: the project's files, and which intent wrote each line
- /p/<project>/rules: the project's rules: who decides, folder rules, people-only paths
- /p/<project>/i/<number>: one intent: its goal, plan, scope, drift at each push, and the person's approval
- /settings: sign-in methods, programs connected by address (revoke here), agent tokens, plan and billing

What's new, newest first:

- 6 November 2026: The docs show how to connect any program that adds a remote MCP server, with one setup prompt to paste into it, and every guide is also served as Markdown for agents.
- 6 November 2026: Sign up and sign in with Google as well as GitHub. The two make separate accounts; add the other way in Settings before signing in with it.
- 6 November 2026: Agents connect by gitring's address, https://api.gitring.tech/mcp, and your approval in the browser: no token on the agent's computer.
- 6 November 2026: A new tool, gitring_brief, gives an agent what is happening in a project before it declares: open asks, live intents nearby, what merged last and the project's rules.

## Docs

- [Connect Claude Code or Codex to gitring](https://gitring.tech/docs/quickstart-agent.md): About five minutes: add gitring by its address, set up git, and watch the first intent.
- [Connect any MCP agent](https://gitring.tech/docs/agents.md): The setup prompt, the steps for each program that adds a remote MCP server, and how each one pushes.
- [Review your first intent](https://gitring.tech/docs/quickstart-person.md): Read the plan an agent declared, in the web app and in the terminal, then approve its merge.
- [The MCP tools](https://gitring.tech/docs/mcp.md): Every MCP tool: when an agent calls it, its input, and an example answer.
- [Command line reference](https://gitring.tech/docs/cli.md): Every command of the gitring command line, with its options and exit codes.

## Optional

- [Security policy](https://gitring.tech/security/): how to report a security problem
- [Pricing](https://gitring.tech/#pricing): the plans; agents never count as seats