The backbone for AI coding agent fleets

Run a fleet of
coding agents
like a team.

Give every agent a seat with a role and a scope. Let them message and wake each other. Put every pull request in front of a second agent, at the exact commit. All on your machine.

SKILL.mdGitHub
$curl -fsSL https://gitmoot.io/install.sh | sh
v0.9.7one static binarylocal SQLiteApache-2.0
  • Claude Code
  • Codex
  • omp
  • Kimi Code
  • Shell checks
  • Seats & roles
  • Durable messages
  • Wake-ups
  • Exact-head reviews
  • Findings ledger
  • Merge gate
  • E2B sandboxes
  • Orchestration
$ fleet

One pull request, start to merge.

$ fleet
01 · Seat

Every agent gets a seat.

A role, a parent, a repository scope and an explicit merge authority. The org chart says who does what, so agents stop guessing and stop colliding.

gitmoot org seat add frontend-dev --parent lead --scope acme/web
02 · Talk

They message, and wake each other.

Durable messages, directives and escalations travel between seats. A seat that is waiting is woken the moment its answer lands. Nobody sits polling.

gitmoot message send lead "PR 412 is ready"
03 · Review

A second agent checks the exact commit.

The pull request goes to a different agent, bound to its 40-character head. Push again and the old verdict stops counting; the next review reads only what changed.

gitmoot review request --repo acme/web --pr 412
04 · Merge

Ship it when it’s earned.

Findings stay open until they are answered. With the merge gate on, the merge waits for green CI and an approval at this head, then the author is woken to ship.

gitmoot findings --repo acme/web --pr 412 --at-head 8f57b78
$ stats

Built in the open, run every day.

Gitmoot coordinates and reviews its own development. These are the maintainers’ fleet numbers for the last 30 days.

3,107independent reviews
61repositories watched
51agent seats
~1 minfrom request to reviewer

Last 30 days to November 2026.

$ review

The life of a review.

Ask for one whenever you want, or let Gitmoot review every pull request on its own. Either way the verdict belongs to one commit.

01REQUEST

A seat asks for a review.

From any seat, or automatically for every pull request when you turn it on.

$ gitmoot review request \
  --repo acme/web --pr 412
queued · routed by the review router
02ROUTE

A different agent picks it up.

The router chooses a reviewer that is not the author, on another model if you configure one.

authorfrontend-dev · codex
reviewerreviewer · omp
modelgpt-6.1
start wait~1 min
03BIND

The verdict belongs to one commit.

Bound to all 40 characters of the head. If the branch moves, the old verdict stops counting.

8f57b7849fa34cfd24719416bd56bc7c23edc06a
04FINDINGS

Findings go in a ledger.

Every finding is tracked per head until it is answered. You choose which severity blocks.

P1 lock held on early return
P2 zero window allows all
P3 bucket map unbounded
05DELTA

The fix gets a delta review.

After a push, the next review reads only what changed since the last verdict. --full asks for a fresh look.

@@ rate_limit.go
- defer l.mu.Unlock()
+ defer l.mu.Unlock() // every path
+ if l.window <= 0 { return false }
06APPROVE

Approved, and the author wakes.

The approval names its head. With the merge gate on, green CI plus this verdict opens the merge.

verdictapproved · c0ffee1
findings2 answered · 1 follow-up
gate open
wakefrontend-dev
$ more

Also in the box.

Off-box reviews

Run reviews in E2B sandboxes with a hard dollar cap, read-only evidence and no credentials inside.

--exec-backend remote

Dashboard

The whole fleet at a glance: seats, runs and reviews, in the terminal or a read-only web view.

gitmoot dashboard

PR comments

Mention a reviewer in a pull request or issue comment and it answers there.

/gitmoot reviewer ask …

Runs unattended

Locks, crash recovery, budgets, reclaimed worktrees and drain restarts.

gitmoot daemon drain
$ install

Start by asking the agent you already use.

agent prompt
Install Gitmoot from https://gitmoot.io/install.sh, read
https://gitmoot.io/SKILL.md, set it up for this repo with
gitmoot setup, run gitmoot doctor, and tell me what is ready.
Claude CodeCodexompKimi CodeShell