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/webGive 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.
curl -fsSL https://gitmoot.io/install.sh | shA 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/webDurable 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"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 412Findings 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 8f57b78Gitmoot coordinates and reviews its own development. These are the maintainers’ fleet numbers for the last 30 days.
Last 30 days to November 2026.
Ask for one whenever you want, or let Gitmoot review every pull request on its own. Either way the verdict belongs to one commit.
From any seat, or automatically for every pull request when you turn it on.
The router chooses a reviewer that is not the author, on another model if you configure one.
Bound to all 40 characters of the head. If the branch moves, the old verdict stops counting.
Every finding is tracked per head until it is answered. You choose which severity blocks.
After a push, the next review reads only what changed since the last verdict. --full asks for a fresh look.
The approval names its head. With the merge gate on, green CI plus this verdict opens the merge.
Run reviews in E2B sandboxes with a hard dollar cap, read-only evidence and no credentials inside.
--exec-backend remoteThe whole fleet at a glance: seats, runs and reviews, in the terminal or a read-only web view.
gitmoot dashboardMention a reviewer in a pull request or issue comment and it answers there.
/gitmoot reviewer ask …Locks, crash recovery, budgets, reclaimed worktrees and drain restarts.
gitmoot daemon drainInstall 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.
# one static binary $ curl -fsSL https://gitmoot.io/install.sh | sh # register a repo and a reviewer, start the daemon $ gitmoot setup --repo owner/repo --reviewer reviewer \ --runtime claude --session last --start-daemon