boo

A terminal dashboard of your open pull requests: the approval, each reviewer (bot or person), the checks, and the review quotas. It also retries CodeRabbit by itself after its quota comes back.

The pull requests that your agents open collect reviews from several bots. Some bots are out of quota, some review in several passes, and some leave a red check that tells nothing about the code. boo reads all of it for each pull request, and shows one line of state, one line of reviewers, and the checks. It is the page https://github.com/pulls/authored, with the review state in it, for you and for the GitHub Apps that open pull requests for you.

Installation

git clone https://github.com/sakuga-software/boo.git
cd boo
pnpm install          # the prepare script builds dist/
ln -sf "$PWD/dist/cli.js" ~/.local/bin/boo

Requires Node 22 or later and an authenticated gh (gh auth status). The Copilot review request (c) needs gh 2.88 or later.

Usage

boo                     # show the state once, retry CodeRabbit if its quota is back, then quit
boo --watch             # stay open until Ctrl+C, and refresh
boo --org all           # all organizations; the default organization is sakuga-software
boo --since 2026-09-15  # only the pull requests created on or after this date
boo --author @me --author app/my-agent  # the pull requests of these authors, for this run
boo --dry-run           # post and merge nothing
boo --help              # options, states and marks

What a row shows

✔  ready to merge     web#921  feat(search): filter the results by date   ✔ 10/10 checks  2/2 on head · 2 reviews
                      last coderabbitai just now  ✔ coderabbitai  ✔ greptile

• The state of the pull request, from the first that applies: conflicts, changes requested, checks failing, ready to merge, approved, reviewing, reviewed, quota, awaiting review. A pull request that leaves the list shows merged, closed or draft. These three are hidden by default: h shows them.
• The checks of the last commit: passed, running or failing.
• The reviewers that reviewed the last commit, out of all the reviewers, and the count of reviews.
• The last reviewer and the age of their review.
• One mark for each reviewer: ✔ approved, ✎ changes requested, ● commented on the last commit; ⟳ reviewing, with 2/3 if the bot shows its progress; ◷ out of quota, with the return time if the notice gives one; ↻ CodeRabbit to retry; ○ requested; ◌ reviewed an older commit only (✔ old if its approval still stands); ⊘ skipped; ‖ paused.
• The place in the stack, for a pull request that merges into another listed pull request.

Stacks

A pull request is stacked on another if it merges into the head branch of the other, in the same repository. The list shows the stack under its bottom pull request, with a line that joins them. All the pull requests above the bottom one have the same indent, at each height of the stack, and each one comes after the pull request that it merges into:

✔  ready to merge     web#921  feat(a)                       stack of 3  ✔ 10/10 checks
├─ ⟳  reviewing          web#924  feat(b)                 on #921 · 2/3  ✔ 6/6 checks
└─ ◷  quota              web#930  feat(c)                 on #924 · 3/3  ◌ 2/8 running

• The bottom pull request shows the size of the stack. Each other one shows the pull request under it, and its place in the stack if the stack has no fork.
• A pull request whose base is not the default branch, but no listed pull request, shows that base: on feat/x.
• The details of a stacked pull request give the state of the pull request under it.
• Before you merge a stacked pull request, the confirmation warns that the merge lands in the branch under it, not in the default branch.
• If the pull request under it is hidden, such as a merged one, the stacked pull request shows as a root. h shows the tree again.
• A narrow terminal drops the text of the place in the stack, but it keeps the tree lines.

The ghost at the top left asks the terminal for its background color (OSC 11, or COLORFGBG) and picks colors that read on it. A terminal that does not answer gets colors that read on both.

In a terminal, the selected row also shows its details: the names of the failing checks, the protection rule that blocks the merge, and the quota return times.

A narrow terminal shows less of each row, from the least useful part:

Width	The row drops
below 120 columns	the reviewers on head and the review count
below 100 columns	the name of the state (the icon stays) and the word "checks"
below 80 columns	the last reviewer, the text of the place in the stack, and the labels of the action bar
below 60 columns	the checks

Settings

Press , to open the settings. ↑ ↓ choose a line, Space or Enter changes it, , or Esc closes the panel. The tool saves them in ~/.config/boo/settings.json (or under $XDG_CONFIG_HOME).

• Hide the merged, the closed and the draft pull requests, each on its own. All three are on.

• Show the checks, the reviewers on head and the review count, the last reviewer, the mark of each reviewer, and the details of the selected pull request. A narrow terminal can still hide them.

• Compact rows: no blank line between the pull requests.

• Show each stacked pull request under the pull request that it merges into. It is on. Off, the list keeps its order, but the details and the merge confirmation still name the pull request under it.

• The authors of the listed pull requests. Space or Enter on this line starts the change: type the authors with a comma between two, then Enter saves and Esc cancels. The list follows the new authors at once.

An author is a login, @me (the account of gh), or app/<slug> for a GitHub App. The default is @me. --author replaces the list at the start of one run. The file holds the authors as a list:

{ "authors": ["@me", "app/my-agent"] }

Review bots

The settings list the review bots of the action bar, with their key, the way the tool asks them, and their logins.

• Space or Enter turns a bot on or off. A bot that is off leaves the list of the review bots, and CodeRabbit gets no more automatic retries. The tool still shows the bot as a reviewer.
• a turns the automatic retry of a bot on or off. It is on for CodeRabbit only. See Retries of the other bots.
• + add a review bot opens a form of five fields. Enter goes to the next field, Esc cancels:
  1. the name that the bar shows;
  2. the key that opens its menu: one letter or one digit that no other bot and no other action uses;
  3. its GitHub logins, with a comma between two, such as sourcery-ai[bot]. The bar dims the bot on a pull request where no reviewer has one of these logins;
  4. the way to ask it: @mention posts @mention <command>, / posts /<command>, and a login asks GitHub for a review by that login (gh pr edit --add-reviewer). A review request has no command, so the form stops there;
  5. its commands, with a comma between two. The first one asks for a review: the automatic retry posts it. Each command takes the first free letter of its name as its key.
• d deletes a bot that you added. A known bot can only be turned off.

The file holds the switches by bot, and the bots that you added:

{
  "bots": { "greptile": { "enabled": false }, "copilot": { "autoRetry": true } },
  "customBots": [
    {
      "name": "Sourcery",
      "key": "s",
      "logins": ["sourcery-ai[bot]"],
      "mention": "@sourcery-ai",
      "commands": ["review", "summary"]
    }
  ]
}

Rules

Reviewers

• A reviewer is a person or a bot that submitted a review, that GitHub asks for a review, CodeRabbit if it commented, or PR-Agent if it posted its review comment. The tool knows no list of bots, so a new reviewer needs no change. A bot that only comments, such as Linear or a preview deployment, is not a reviewer.
• The author of the pull request is not a reviewer: their reviews are replies in the threads.
• A review whose line comments all answer an earlier comment is a reply in a thread, not a review. A review with an empty body and its own line comments is a review: Greptile puts all its findings on the lines.
• A review that says quota, rate limit, limit reached, unable to review or usage limit in its first paragraph is a refusal, not a review. A real review can quote the quota of another reviewer further down, so the rest of the body does not count.
• A reviewer reviews now if it has a running check with its name (claude-review for sakuga-claude-review[bot]), or if its last review or comment shows a progress below its total (2/3 files) on its first line. A progress further down is a quote, a list or an example.

PR-Agent

PR-Agent submits no GitHub review: its review is one comment ("PR Reviewer Guide"), which it edits at each new review. The login of that comment is the reviewer, so each install works under its own name (sakuga-review[bot] at Sakuga).

• The mark comes from the "Merge recommendation" line: Safe to merge gives ✔, Changes required gives ✎, and all the rest, or no such line, gives ●. It is the opinion of a model, not a GitHub verdict: it gives no approved, no ready to merge and no changes requested state to the pull request.
• An edited comment names the commit that it covers ("Review updated until commit …"). If that commit is not the head commit, the review is stale (◌).
• A comment with no edit covers the head commit, unless the head commit has checks with pr-agent in their name and none of them passed: then the review is stale.
• A running check with pr-agent in its name on the head commit means that PR-Agent reviews now (⟳).
• The line suggestions of /improve count as reviews, but do not change the mark.

Approval and checks

• The approval follows the rule of GitHub: the last review of each reviewer that approves, requests changes or is dismissed stands, on any commit. One request for changes wins over all the approvals. A later comment review, such as a reply, does not replace a verdict.
• ready to merge needs an approval, no request for changes, no failing or running check, and a merge state that GitHub accepts (clean, unstable or has_hooks).
• A check counts as a quota check, and not as a failure, if its description names a quota (CodeRabbit: "Review rate limited"), or if it fails and belongs to a reviewer that refused for quota. A red check of a refused reviewer tells nothing about the code.

Retries of the other bots

The automatic retry of a bot other than CodeRabbit is off by default. When it is on:

• the bot gets a retry if its last review of the pull request is a quota refusal;
• the retry waits for the return time that the refusal gives, or 1 hour after the refusal if it gives no time;
• the tool posts the first command of the bot, or asks GitHub for a review if the bot takes review requests (Copilot);
• each refusal gets one retry only. A new refusal after the retry gives a new retry.
• if the post fails, for example because the bot is not a collaborator, a red message says why, and the tool tries again 5 minutes later.

With --watch, the details of the selected pull request show the time of each planned retry. Without --watch, the tool posts only the retries that are due, and then stops.

CodeRabbit retries

CodeRabbit is the reviewer that the tool can ask again by itself.

• A commit counts as reviewed if CodeRabbit submitted a GitHub review on it, or if its summary says that a finished review covered it (final_review_risk_coverage).
• A summary that says "Review skipped" (a bot author, a draft) gives ⊘ with the reason. "Reviews paused" gives ‖. The tool retries neither by itself: CodeRabbit chose not to review. Press r to ask once.
• The delay comes from the current version of the CodeRabbit comment. Its "available in …" starts at the last edit of the comment (updated_at).
• Only a bare @coderabbitai review comment counts as a request. If the comment has more text, CodeRabbit replies as a chat and starts no review.
• If a request has no reply after 15 min, it no longer blocks a retry.
• A review or a "Review triggered" reply after a rate limit lifts that rate limit.
• The quota belongs to the developer (the pull request author), on a rolling window. On the CodeRabbit "Open source" plan, it is also scoped per repository: the tool reads the "Plan:" line of the CodeRabbit comments and keeps such a repository on its own clock. The tool reads one quota clock from the CodeRabbit comments of all the listed pull requests in the same scope:
  • a notice with a delay ("Next included review available in …", in the first CodeRabbit comment, which CodeRabbit edits at each rate limit) gives the time when the quota comes back. The tool adds 30 s: CodeRabbit rounds its delays, and a request 4 s after the time can be refused;
  • a refused command with no delay ("Review rate limited.") only dates the refusal;
  • "N remain after this review" on a settled summary, after the refusal, means the quota is back. The tool dates it by the review, because a later edit of the summary can keep the line.
• When the time comes from another pull request, the details say so ("read on web#517 at 17:19").
• If a refusal came after the time that the newest notice gave, the tool assumes 1 hour.
• The tool only sees the pull requests that it lists. A review on a pull request outside the list spends the same quota, and the tool does not see it.
• The tool posts one request at a time, and polls for the reply to each one for about 90 s. A new rate limit puts the other pull requests on hold.

Watch

• The tool searches the pull requests again once a minute. It adds the new ones, and shows the ones that are merged, closed or back to draft. It never posts on those. A draft that is ready for review again comes back into the watch.
• It reads each pull request again once a minute, and every 30 s while a reviewer reviews or a check runs.
• It reads each pull request with one GraphQL query of cost 1. Ten pull requests cost about 600 points an hour, out of the 5,000 of the GraphQL limit. The REST limit, which gh commands of your agents use, stays free.

Keys and mouse

With --watch in a terminal, the tool opens in full screen and takes keys and mouse clicks. The counts and the action bar stay at the bottom of the window. Piped or scheduled runs stay as they are.

The action bar has three levels. The main set shows open, merge, refresh, the hidden pull requests and the settings. → or Space shows the list of the review bots. The key of a bot opens the menu of that bot, with its commands. ← or Space goes back one level, and Esc goes back to the main set.

A key of a bot or of a command works only at the level that shows it, so two bots can use the same key. The keys of the main set work at every level, except r: in the bot levels, r belongs to the bots.

Key	Action
↑ ↓ or k j	select a pull request (the mouse wheel does it too)
o or Enter	open the pull request in the browser
m	merge the pull request: squash if the repository allows it, else merge, else rebase
r	read the list and every pull request again now, in the main set only
h	show or hide the merged, closed and draft pull requests
,	open the settings
→ or Space	show the list of the review bots
← or Space	go back one level
Esc	go back to the main set
q	quit

In the list of the review bots:

Key	Menu	Commands
r	CodeRabbit	r posts @coderabbitai review, f posts @coderabbitai full review, a posts @coderabbitai approve (resolve the CodeRabbit threads, then approve), s posts @coderabbitai resolve (resolve the CodeRabbit threads)
g	Greptile	r posts @greptileai review
c	Copilot	r asks Copilot for a review (gh pr edit --add-reviewer @copilot, needs gh 2.88 or later)
p	PR-Agent	r posts /review (PR-Agent reviews the pull request again), i posts /improve (PR-Agent suggests code changes on the lines)

A command to a bot that takes its commands in a comment, such as CodeRabbit, Greptile or PR-Agent, works only on a pull request that the bot reviews; the bar dims the bot and its commands on the other ones. Copilot gets a review request from GitHub and not a comment: a mention of @copilot starts its coding agent. The detection of the reviewers keeps no list of bots, but the list of the review bots does: only these four bots, and the bots that you add in the settings, have a known command. A CodeRabbit post goes through the queue of the automatic retries. A post to another bot goes at once, because it does not spend the CodeRabbit quota.

Each post and each merge asks for a confirmation: y or Enter confirms, n or Esc cancels. Before a merge, the confirmation warns about a request for changes, a missing approval, a failing or running check, a conflict, a protection rule, a branch behind its base, or a base that is not the default branch (a stacked pull request). You can still merge: GitHub enforces the protection rules anyway. The repository settings decide if GitHub deletes the branch. A click selects a row, presses a button of the bar, or changes a line of the settings. The mouse mode takes over text selection: hold Shift or Option, depending on the terminal, to select text. A merged or closed pull request accepts only o, and --dry-run disables every post and every merge.

Development

pnpm dev -- --dry-run   # run the sources with tsx
pnpm test               # tests of the decision logic
pnpm typecheck
pnpm lint               # oxlint
pnpm format             # oxfmt --check; pnpm format:fix writes the files

Demo

The GIF uses the real interface and the real decision logic with a fake GitHub (demo/demo.tsx). The fake GitHub plays a timeline: a CodeRabbit review in progress, a bot that shows its progress, a Copilot quota refusal, a CodeRabbit quota that comes back and a retry, a merged pull request, a new pull request, then the reviews. At the end, it shows the list of the review bots with →, selects a pull request with the arrow keys, opens the CodeRabbit menu with r, and posts @coderabbitai approve with a, then Enter. To see it live, run pnpm demo. To record the GIF again (requires vhs, ttyd and ffmpeg):

demo/record.sh