Repository navigation
Code Review Workspace 1.8.0
Review a thread's work in its folder on any machine, send your comments to the thread that wrote the code and get each fix back checked, and have the review agent do review work on GitHub when you ask. Now BB 0.48+ (plugin SDK 0.6.79+) with Node 24+, where it was BB 0.45+ (SDK 0.6.14+); installs at ^1.0.0 update to 1.8.0. 1.8.0 adds no migration. To have the agent only draft again, turn off Let the review agent act when you ask, which takes effect at once; if the agent should only draft for everyone, 1.8.1 would be 1.8.0 with that switch off by default, which installs at ^1.0.0 take, keeping every review and setting. Don't remove and reinstall the plugin: that deletes its settings and secrets. Should 1.7.0's code ever be shipped again, it reads 1.8.0's reviews, with a folder's review on its last snapshot, but a comment it edits loses its id and where its fix stood, Mark as pre-existing and Mark as from this PR fail on any comment 1.8.0 sent, and Submit would post every comment still in the draft, including those sent, resolved or dismissed. Its prune drops the Sends' and Not pushed yet's snapshots, so back on 1.8, Since your last Send shows the whole diff, and Push on your PR warns until you open Not pushed yet again.
The review agent acts when you ask
- The review agent does review work when you ask it, where it only drafted: on any PR it posts replies and PR comments, resolves threads, and submits your review, and it also merges, after the Post form; on your own PRs it also changes the title, description, labels, reviewers and assignees, and closes, reopens or marks it ready or draft; on a folder's review it opens the PR. "Agents draft; only you post" gives way to this. Let the review agent act when you ask, in Settings → Review agent, on by default, turns it off: the agent then only drafts, told never to post, as in 1.7.0, and an agent already running takes the change at once.
- What posts under your name shows first, in a form in place of the agent's message box: what it does, where and as whom, "Approve
flosports/api#4512as @you", then exactly what posts, with one button, Post, Approve, Merge and the like, and Don't post. A short yes you type posts what it showed, once; "just post it" skips the form, and for an approve, request changes, merge or close only when it's your whole message. Text that changed since it was shown is shown again. - Only your own message or click in that review approves, merges or closes. Asks your other threads relay, with
bb thread tell(the agent's thread isagentThreadIdinbb review list --json) or the newbb review ask, count as yours for replies, comments, Comment and Request changes reviews and your PR's details: what would post goes back to that thread first, and its yes posts it. A relayed approve, merge or close, or one from the newbb review approve <review…>, waits in Needs review as Ready to approve, with exactly what posts and the thread that asked; Approve N posts each approval shown, holding a PR with commits since you read it until Approve them too. - Turns the plugin starts on its own, the automatic review, new-commit checks and the checks it runs itself, only draft: the agent's verdict is its suggestion, and nothing posts, sends, or changes your comments. So does any turn it can't place, a message from a review's own agents, and one carrying text the plugin put in it, as a quoted selection, which never confirms a post.
- A risky ask, as a merge while checks run, a force-push, or a teammate's labels, or merging their PR, gets one pushback with a better route, then happens your way. A merge happens only at the commit you reviewed.
- What the agent did on GitHub is listed under Agent activity in Finish review, with links and the thread that asked.
- Writes to GitHub go one at a time, a second apart, waiting out rate limits, and GitHub's refusals say what to do. A reply GitHub already has isn't sent again for 15 minutes. Setup says when your token lacks
repoorread:org.
Warnings instead of blocks
- Submit warns, keeping your draft, where it refused: on new commits or a new base (Submit anyway posts on the commit you reviewed, and an approval says how many commits it covers that you haven't seen; See the N commits), on comments on an older diff or outside it (Submit anyway moves them into the summary), a merged or closed PR, or a guide rebuilding. On your own PR it offers Submit as Comment, and with a pending review on github.com, Open it on GitHub. What GitHub refuses still stops it.
- Send and Fix in a new thread work on someone else's PR after a warning (Send anyway), where they were offered only on your own changes; your review on GitHub isn't changed. A Send to an archived or deleted main thread offers Unarchive and send or Start a fresh thread, where it refused.
Review a thread's folder
bb reviewwith nothing after it reviews the folder its thread works in, on any machine: one review per folder and branch, however many threads and subagents work there, committed, uncommitted and new files alike, against the branch's PR's base, else the one BB keeps. Run again, it opens the review as it is. It's named after the main thread, the top thread in the folder, and its id isapi:branch.- Review changes, above a thread's message box in BB, after Changed files, starts or opens that folder's review, then reads "Review · 2 open". A thread linked to a review gets a Review tab beside its chat, with its comments and the review agent's chat. Review changes above a thread's message box in Settings → Reading hides the first.
- New files that look like secrets (
.env*,*.pem,*.key,credentials*), binaries and very large ones stay out of the review and away from the agents until you bring them in; committed ones that look like secrets are flagged. The review agent never reads through a changed link. - The notice strip says when the folder's code changed, with Update, which keeps the guide and moves your comments; when it's on another branch, which pauses the review; when its machine is offline, keeping what it last read; when BB removed it; and which other threads are editing it. Rewrite guide has the guide writer write a new one, and a checkout review's "The code changed." offers both, where Update rewrote the guide.
- Push, in Finish review, has the main thread commit what you reviewed and report the commit, checks it against the review, every file the branch commits, ones the review hid as a
.envincluded, and secrets an earlier commit on the branch added, then has the thread push exactly that commit,git push origin '<sha>:refs/heads/<branch>', never forced. A mismatch warns first, "Not pushed. 3 files changed since you reviewed.", with Update first and Push anyway; then the review says whether GitHub is at that commit. New commits on GitHub that didn't come from Push get a note, with Update and Got it. On your own PR, a fresh or forked thread pushes the same way, checked against Not pushed yet. - Once the branch has an open PR, the same review becomes the PR's, its id
api#4512, your comments kept. Open PR, in Finish review, has the review agent draft the PR for the Post form.
Send comments to the main thread
- Send N to main thread in Finish review, and Send now on a comment, send your comments to the review's main thread, the thread that writes the code, each with an id, its lines and code, after whatever it's doing. The Main thread tab, in BB's title bar or the phone's dock, shows its chat beside the diff, with Change to pick another thread or start a fresh one.
- The thread reports each comment with
bb review report <id> done|declined --note …, andbb review readyonce it's finished. Then the review comes back Ready to re-review, with an alert, once the review agent has checked each fix against the code since its Send; idle before that, as while subagents work, it says "1 of 6 reported" with Check now, and with the thread archived, Send the rest to a fresh thread. - A Send ends "Don't push until I say" again, reversing 1.4.0's "that thread keeps its own rules about GitHub" (PR #7); Let it push when done, in its picker, drops the line, restoring it.
- Each comment you sent says where it stands, on its card, row and pill: queued, sent, done or declined with the thread's note, or "Looks done · not reported" where the check inferred it, and the card says which thread reported it, the commit it named, and what the review agent's check found against that Send. Edited, it's open again for the next Send.
- Resolve, Dismiss and Reopen on a sent comment's card are your clicks alone; no agent, command or report resolves a comment. Undo, right after Resolve or Dismiss, puts it back as sent, or open if it was edited since. A reopened comment goes with the next Send, and Undo after Remove keeps a comment's id and where its fix stood. A sent comment the thread declined, or the check found not or partly addressed, waits in Needs you. Comments' chips filter by where fixes stand: Open, Sent, Done, Declined, Resolved, Dismissed.
- On your own change, Submit posts only open comments: those sent to the main thread, resolved or dismissed stay in BB: Submit's checks, what it posts and Finish review's counts leave them out, and Submit anyway never moves them into the summary. On a PR you don't own, a Send changes nothing Submit posts; a comment you resolve or dismiss there doesn't post. Submit refuses a draft with sent comments while it can't tell whether the PR is yours.
- Asked to fix a comment, the review agent sends it with Send now; told "you do it", it writes the exact patch, which goes with that comment's Send for the thread to apply as written.
- Since your last Send, in the compare menu, shows what changed since the diff your last Send went with.
Your own PRs
- Your open PRs join All reviews from GitHub, with everyone's threads, review summaries and PR comments (Include your own PRs, in Settings → Whose turn). A person's comment waiting for your reply brings your PR to Needs review as Your PR · 3 new comments in 2 threads, with one alert, and reads "Needs your reply to @sam"; a bot's never does. With nothing waiting, it's under Reviewed. On your own PR, the check strip and "Yours: … handled" give way to the Send loop below.
- Send on a teammate's comment takes their words, quoted as theirs, to the PR's main thread; with none, to a fresh thread at the PR's head commit, told about the PR and the comments, or a fork of the thread that wrote it. Not pushed yet shows what that thread has that GitHub doesn't, and Branch kept says what's left once BB removes its worktree.
Which review you're in
- Every review goes by a short id,
api#4512, orapi:feat/snooze-checksfor local work, a bb branch read as its slug, and the owner or the folder's end added where two would read the same. BB's title bar and the window's title lead with it,api#4512 · Fix login race, so split panes and windows read apart; the band keeps it in a chip, and the list's rows, Needs You alerts, the review agent's and Fix in a new thread threads, what Send sends, the Post form andbb review(an id column inlist,idin its JSON) name the review by it. - Rename a review from the pencil beside its Overview's title, or with
bb review <target> --name "…". Screen readers hear the whole review, "Pull request 4512 in flosports/api: Fix login race, by dana", in its landmark and the band.