# How to stand up a shared server for a fleet of coding agents with git-ai

Repo: [feder-cr/git-ai](https://github.com/feder-cr/git-ai) | Difficulty: Advanced | Time: 1 hour | Basis: Seen in the wild

Run your own gitai server so each agent gets its own token and lands onto shared branches.

**Who it is for:** Team lead whose parallel coding agents keep rebasing and retrying against one main branch

**The problem:** A normal Git host makes every agent clone fully and fight over pushes, so throughput collapses as agent count grows.

**The outcome:** You have a gitai server running from a config file, with agents landing on it through the graft CLI instead of pushing to a classic host.

## Steps

1. Copy examples/graft/config.toml and adapt it to your paths
2. Start the server with: _build/bin/gitaly serve config.toml
3. Use the graft CLI (./_build/bin/graft) from each agent to clone and land
4. Read doc/graft/AGENT-SECURITY.md for tokens and the RPC allowlist

## Prompt to paste into your agent

```text
Using feder-cr/git-ai, adapt examples/graft/config.toml for a server at <data-dir> and start it with _build/bin/gitaly serve. Show how an agent clones and lands one change, and verify the server accepted it.
```

## Caveat

The README states version 0.2.0 and says interfaces may change before 1.0, so treat a real production repo with caution.

## Seen in the wild

- X (Oct 2026): https://x.com/i/web/status/2112080627617202280
- X (Oct 2026): https://x.com/i/web/status/2111828392513274064

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/feder-cr-git-ai/host-a-shared-repo-for-agent-fleet/