Repository navigation
Releases
Code Review Workspace 1.13.0
Review with focuses, opt-in: independent agents each check the diff for one thing, such as docs, bugs or security, and the review agent confirms their findings before drafting comments, each labelled with the focus that raised it. Still BB 0.48+ (plugin SDK 0.6.79+) with Node 24+; installs at ^1.0.0 update to 1.13.0. 1.13.0 adds three migrations (40–42) on SQLite and on Postgres; back up before updating. 1.12.1 has no startup guard, so returning to it isn't covered by a simple downgrade; see Data and recovery below.
- Full-permission focuses, opt-in: Settings → Focuses can allow
fullwhen a provider has no restricted mode (including Pi). Off by default, with a warning about shell commands, file edits and untrusted PR text; restricted modes remain preferred. No migration; guide-writer permissions are unchanged. - Six more focus templates: Repo rules, Bugs (an independent second bug pass), Error handling, Tests, Types, and Security join Docs in Settings and Add focus. All six start disabled; Docs stays enabled in the default list. Saved lists are unchanged. Pinned sources, change notices and Apache/MIT license copies ship with the templates.
- Focuses, Phases 0–4: opt-in groundwork and stored findings; restricted focus workers and review-agent confirmation; optional focus labels in GitHub posting previews; progress, coverage and recovery in the review; and a Settings editor for instructions and execution choices, including on phones. Focuses do not rerun automatically on pushes. Their lowest provider permissions can still allow edits in the review checkout.
- Startup safety: SQLite and Postgres refuse a database with an unknown migration id or a changed recorded statement hash before migrating or writing the Store. Missing trailing migrations still upgrade normally; legacy SQLite hashes are adopted by BB as before. PR and main CI run typecheck, tests and lint.
- Data and recovery: three additive migrations (40–42) add focus threads, findings and preferences. Back up before updating. Repair forward while retaining migration history; the guard does not undo migrations or protect released 1.12.1. Returning to pre-focus code requires stopping workers and restoring a consistent pre-focus snapshot; later edits can be lost. See the runbook.
Code Review Workspace 1.12.1
The Ask agent button opens the review agent's chat empty. Still BB 0.48+ (plugin SDK 0.6.79+) with Node 24+; installs at ^1.0.0 update to 1.12.1. 1.12.1 adds no migration, so rolling back to 1.12.0 keeps everything.
- Ask agent in the title bar or the phone's dock, or the
akey, no longer puts "Aboutfile." for the file in view into your message, or a context chip naming it over the first message's box. Selections and a failing check's Ask agent still quote what they ask about.
Code Review Workspace 1.12.0
One review of a PR and your local changes to it, comments that go to the thread that asked, a discussion with the agent you can see into and go on with, and a Finish review whose signals agree and that no longer asks about chapters you read quickly. Still BB 0.48+ (plugin SDK 0.6.79+) with Node 24+; installs at ^1.0.0 update to 1.12.0. 1.12.0 adds one migration, a chapter_reads table, on SQLite and on Postgres; what else it adds is kept with the review's other lifecycle fields and its draft. Rolling back to 1.11.0 keeps every review and setting, and deferrals you confirmed, how long chapters were open and It's fine unused until you update again, except that a draft 1.11.0 changes forgets which of the agent's comments you haven't seen, so they no longer say New from agent; on 1.11.0, bb review storage won't move the reviews between SQLite and Postgres, the migration being newer than it. There a folder that joined someone else's PR's review counts as yours, so Sends to its thread don't ask, comments sent to it don't post with Submit, and Push isn't offered; and a Deferred check shows a blank badge.
Your threads and your local changes
- A sub-thread's review goes to that sub-thread.
bb reviewwith no arguments, or Review changes above its message box, makes the thread you see that asked the review's main thread, even where an orchestrator works in the same folder: its comments, Send now, Main thread ↗ and the review's name are the sub-thread's, and the orchestrator no longer relays them. A hidden subagent's call still goes to the nearest thread you see working in that folder, and a thread working under one of the plugin's agents still can't start a review. A review an orchestrator already has keeps it; Change thread on its Main thread tab moves it to the sub-thread. Where sibling sub-threads work in one folder, their shared parent there is the main thread, as soon as a second of them works there, so no sibling takes the others' comments; the threads over a main thread aren't listed as also editing its folder. - Review changes, or
bb reviewwith no arguments, in a thread on the branch of an open PR you're reviewing already, as a thread you had check out a teammate's PR to change it, joins the PR's review. It started a review of its own beside it, with a second guide writer and review agent, which merged only on your click, and kept itself rather than the PR's. Now the folder is attached to the PR's review, the thread becomes its main thread, the one before kept, nothing is rebuilt, and Review changes opens the review on Not pushed yet: what the folder has that the PR's head on GitHub doesn't, committed or not. It joins the review of the PR PR Status names for the branch, else of the repo's open PR whose head is the branch, not from a fork, while the review has a guide, or one being written, and no folder of its own, and the folder has the PR's head; otherwise the folder gets a review of its own, as before. - It's still the author's PR: comments you send to the thread post with Submit unless you resolve or dismiss them, and a Send quotes the author's code as theirs. A Send to your thread there doesn't ask first, as Sends on someone else's PR do.
- Push works there, from the folder, and says first "This is @dana's PR: Push puts the commit on their branch,
feat/qa. Push anyway to go on.", with Push anyway and Cancel. A head in someone's fork goes to that fork's remote. Let it push when done on a Send asks first there too, and a Send that lets the thread push tells it whose branch a push changes. - The review agent is told the folder joined the review, where its instructions said a PR's review with a folder began as it. The skill agents in your threads read says to run
bb reviewthere for you to see their local changes to a PR.reviewThreadChangesanswersjoined: truewhen the folder joined.
Discussions with the agent
- Ask agent on a comment or the summary says what the agent gets with your words: "It sees this comment and line 192.", "It sees lines 1–2.", or "It sees the summary and the draft comments."
- "Agent edited the comment." and "Agent edited the summary." have Show changes, which strikes the words the edit took out and marks the ones it put in.
- The agent answers each question you ask in a discussion, and after an edit says in a sentence what it changed, where it could skip a reply before.
- A discussion with the agent ends with Reply, as a GitHub thread does: under a line, in Comments, and under the summary. Ask agent sat above it, among the comment's actions, so it didn't look like you could go on. Reply's box opens in its place, and the focus comes back to Reply once you send or leave it; Ask agent shows until there's a discussion.
- "The agent didn’t reply here." links to the agent's chat as Open its chat, which said Ask agent and read like Reply.
- Dig deeper says what it found once it's done, where the button was: each What to verify item marked holds ✓, problem ⚠ or not verified ?, with the agent's one-line note, its one line overall, the comments it added, each showing its line, and Agent’s reply, which opens its chat. It stays until you Dig deeper again, and says so when the agent stopped before it finished. The review agent reports it with a new tool,
report_deep_dive.
What the agent posts
- The review agent is told the PR's author reads the comments, replies and summary on GitHub and never sees the guide, in a review pass, a re-review's check and Dig deeper, so what it drafts no longer mentions its chapters, Start here, risk levels or what it flagged, which read on GitHub as a reply to a conversation the author never had. A problem the guide pointed to that the agent verifies is still a comment, on its own evidence; a spot that holds up, it tells you in chat.
- The agent raises a finding about a line as a line comment before its summary names it, a re-review's new findings too, so you meet it reading the chapters, and the summary raises nothing they didn't. Under the summary in Finish review, each changed line it cites, such as
playlist.go:192, opens in the code, marked with the severity of the comment there, or Not in your comments when no comment raises it. - A comment the agent adds, in its review, a re-review or while it updates the summary at your ask, is New from agent—not yet reviewed: on its card in the code and in Comments, its pill and row, and on the chip of a summary that cites it. It stays marked until its card has been in view for a moment, or you edit it, on every device, so a finding added at the summary doesn't pass as one you read in the chapters.
Finish review
- While Finish review is open, Submit to GitHub is the one filled button: the last chapter's end and Not pushed yet's drop their Finish review, Mark viewed and finish reads Mark viewed, and every other button that was filled is outlined: every chapter's buttons, the Overview's way in, Send reply, the comment box's Save, Send and Let it push for the main thread, Update first, and the confirms of Move to summary, Replace summary and a notice's recommended choice. On a local review, with no Submit, Send to the main thread stays filled. Finish review in BB's title bar opens the panel, or takes you to it, and never closes it, where a second click closed it. Under Submit, "Your draft stays in BB until you submit, then posts to
flosports/web#4512as @you." A reviewer who saw Finish review beside Submit to GitHub couldn't tell which came first, or whether finishing would close the review before they'd submitted. - On a re-review, the agent's read count is of the files changed since your review, "Read 1 of 2 files changed since your review", and what it read with
read_changes_since_reviewcounts, where it said "Read 0 of 8 files". After a rebase alone it says nothing. - The agent can't suggest Approve while a blocking item is open or unchecked, from its check or
set_review_summary, and a later check that reopens one withdraws the Approve it suggested before, so Finish review no longer shows "Agent suggests Approve" beside Request what's left. A new verdict, Deferred, is for an ask the author, the PR or you say comes later, as in a follow-up PR, quoting where. It's the agent's proposal: "Deferred · not confirmed", in Needs you, still blocks an Approve and stays in Request what's left until you click Confirm deferral on it in Comments (Reopen takes it back). Confirmed, it leaves Needs you and Request what's left, a review with the rest addressed looks ready, and a row's progress says it apart, "1/2 addressed +1 deferred". Request what's left's summary is yours, "Summary · not submitted". - Your last review is history, not a status: "Your last review: Commented · 5h ago · 2 commits since", neutral, with View on GitHub.
- Before you approve, a part of Finish review between Verdict and Goes to GitHub while you approve, lists files in high-risk chapters you haven't viewed and, new, flagged files you haven't viewed: a test that loses assertions or skips tests, a lockfile with a new download host, or hidden bidirectional Unicode ("1 flagged file not viewed: tests weakened."), each with Show, and an Approve the agent suggests without reading every file. Submit asks once more about these. They were under Goes to GitHub, though none of them posts.
- Chapters marked viewed faster than they read are one plain row there, where each was a warning: "Read quickly: chapters 2 and 3 · 373 lines in 2 min", with the riskiest one's first thing to check under it and Show, which opens that chapter. Submit no longer asks about them.
- Tests and docs read at their own pace, 2,000 lines an hour by default, beside 500 for code and config; lockfiles and generated files still don't count. A chapter is judged once all its files ...
Code Review Workspace 1.11.0
See at a glance which reviews are working and which have news, with BB's own thread status icons on their rows. Still BB 0.48+ (plugin SDK 0.6.79+) with Node 24+; installs at ^1.0.0 update to 1.11.0. 1.11.0 adds no migration, so rolling back to 1.10.1 keeps everything; the rows lose their icons there.
- A review's row in BB's thread list, in Needs review or pinned, shows its work where BB's rows show a thread's, with BB's own icons: a spinner while its guide is built or its review agent works, the unread dot once the agent is done and you haven't opened the review since, a red ✕ if it failed, and a question mark while it waits on you, as for its Post form. On hover, where there's a mouse, the pin takes its place, as BB's row actions do. Screen readers hear it in the row's description: "Review agent finished".
- All reviews shows the agent's icon too, before each row's age. A guide being built spins in the row's status line, as before.
- Opening a review reads its agent, as opening a thread does: the dot goes, and stays gone while the review is open in a window in view, however often the agent finishes.
- The agent's thread is hidden from BB's list, which leaves it out of what BB tells plugins too, so the plugin reads it from BB, and the rows hear when it starts, ends, fails or asks you. A message to the agent waiting in its queue shows at the list's next read.
- A review agent that finished before you updated, with nothing read since, shows the dot until you open its review.
Code Review Workspace 1.10.1
Other plugins start a review of a thread's changes through the same contract they read reviews by. Still BB 0.48+ (plugin SDK 0.6.79+) with Node 24+; installs at ^1.0.0 update to 1.10.1. 1.10.1 adds no migration, so rolling back to 1.10.0 keeps everything; reviewThreadChanges answers the same there, though BB's RPC discovery doesn't list it.
reviewThreadChanges, which Review changes above a thread's message box calls, is part of the contract other plugins rely on, docs/plugin-api.md, where it was the panel's own and could change without notice. It keeps its name, takes{ threadId }and answers{ ok, error, targetKey }, as since 1.8.0; its answer may gain fields. BB's RPC discovery lists it besidereviews.v1.status, each field described. Calling it starts a review, so a plugin doesn't probe it: whereverreviews.v1.statusanswers, it does.- docs/plugin-api.md says what it starts or opens, what that costs, and why it refuses; and that on Postgres storage
reviews.v1.statusanswersunknown_methodfor a moment as Code Review Workspace starts, so a plugin asks again on its next poll rather than remember it.
Code Review Workspace 1.10.0
Other plugins read where each review stands with one call, and the lists say who a review waits on in more cases: comments out from a PR's review, your approval in the main thread, a Push under way, and a removed folder. Still BB 0.48+ (plugin SDK 0.6.79+) with Node 24+; installs at ^1.0.0 update to 1.10.0. 1.10.0 adds no migration: when each review came to stand as it does is kept with the review's other lifecycle fields. Rolling back to 1.9.0 keeps every review and setting, and 1.9.0 ignores that field; other plugins' calls of reviews.v1.status then answer unknown_method. As it starts, 1.10.0 ends an approval sent to a main thread for a diff its review no longer shows, as 1.9.0 kept one after Update, and Finish review offers Send approval for that review again, on 1.9.0 too.
For other plugins
reviews.v1.status, a typed method published to BB's RPC discovery, lists every review with who it waits on,user,agentand the thread working on it,authorornobody, whether you've approved the code as it is now, since when, its status as All reviews says it, and the PR, branch, folder and threads it belongs to. A review merged into another names the one that stays. It reads no diff or guide, so it's cheap to poll, and it says what All reviews, the alerts andbb review listsay. docs/plugin-api.md is its contract: within v1 a field may be added, never removed or changed in meaning.listReviewsand the panel's other methods keep their fields, and stay the panel's own.- A plugin tells whether it's there by calling it: before 1.10.0 the call answers HTTP 404,
unknown_method.bb plugin rpc inspect code-review-workspace reviews.v1.statusprints its schemas, each field described.
Who a review waits on
- Comments you send from a PR's review, your own or someone else's, a folder's review that became its PR's among them, wait on the thread fixing them, under Waiting on author as "2 of 6 reported", as a local review's do, where the review stayed in Needs review as Your PR or Ready, or in Reviewed. Something newer that's yours brings it back: a teammate's comment on your PR, a re-request, a question; and your next review on GitHub is the turn, as before.
- An approval you send to the main thread of a local review or your own PR moves the review to Reviewed, Approved, "You approved 2h ago", where it stayed in Needs review. It holds while the code is as you approved it: the folder changing since, as the review checks it when the main thread stops, or new commits on the PR, bring the review back, and so does something newer that's yours, as a teammate's comment. Update, or any new diff, ends the approval, where it was kept and an older diff's approval read as current. A local review that becomes its PR's keeps it when the PR changes the same files the same way, as after Push.
- A Push under way waits on the main thread, Committing for Push, then Pushing to feat/qa, under Waiting on author, where the review kept the turn it had.
- A local review whose folder BB removed, with comments still open or sent, waits on no one, Folder removed under Waiting on author, where it stayed in Needs review. Comments that came back from its main thread, or whose thread was archived or deleted first, still bring it to Needs review.
Code Review Workspace 1.9.0
Go between a review and its main thread in a click or a key, with the review agent and the main thread in BB's own side panel, and keep one review from your local changes through the PR: it now notices the PR whoever opens it, draft PRs included, and still reviews what isn't pushed yet. Still BB 0.48+ (plugin SDK 0.6.79+) with Node 24+; installs at ^1.0.0 update to 1.9.0. 1.9.0 adds no migration: what it adds to a review is kept with the review's other lifecycle fields. Rolling back to 1.8.1 keeps every review and setting, and 1.8.1 keeps 1.9.0's fields and ignores them. A review merged into another shows in Archive as an archived PR review, empty but for a comment a thread tracks that couldn't move, and its PR's link, bb review <url>, opens that one. One that keeps such a comment is saved without its repo, its link kept, so 1.8.1 lists it as #34, and its Submit, the review agent's tools and the sync refuse it: that comment never posts. Back on 1.9.0, Archive names it by its link again. A review with comments not on GitHub yet opens, but its draft doesn't load and Submit stops before anything posts, so none lands on a wrong line; back on 1.9.0, it loads again. 1.8.1's prune drops Not pushed yet's snapshot, and those comments keep their code.
Doing and reviewing, a click apart
- The review agent and the main thread are tabs in BB's own side panel, as on a thread's page, where they were views of the review's panel: one panel at the right for the conversations, BB's. Ask agent (
a) opens the Review agent tab, and the button closes it again; every way in does too, a line, a selection, a comment, a failing check and Open PR. The Main thread tab, beside a review with one, has the thread's chat, Change thread, and Main thread ↗; it shows while the review loads, and not with Send to thread off. Both are headed by the review's id and name, and show the review you're on, switching as you switch reviews. A BB app from before the side panel opens either chat as a thread in a split instead. Comments and Finish review stay in the review's own panel, beside BB's where they fit and over the code where they don't. - Main thread ↗, in BB's title bar and a phone's dock, goes to the main thread, where it opened the main thread's view; Show beside review, after it, shows the Main thread tab instead. The thread's Review · 2 open ↗, now for whichever review its Review tab shows and straight to it, and the tab's Review ↗ come back; the tab's comments open the review at each, and the agent's first message starts there, on the thread. Links to a thread name it, with ↗: Finish review's, the push notice's and Send's read Main thread ↗.
- Send and Send now toasts have Watch, which shows the main thread beside the review, or on a phone goes to it. Change is Change thread, and Finish review's Change main thread opens the tab with its menu open.
- Switch between review and main thread, in BB's command palette with ⌘⇧. (Ctrl+Shift+.), goes from a thread's page to its review, and from a review's page to its main thread. It's listed only where there's one to go to.
- The review agent's floating widget is gone, with Pop out and Dock: BB's panel docks beside the code on a desktop and an iPad, and covers the page on a phone. A first message you haven't sent stays while BB's panel closes; BB keeps an unsent reply in either chat, as on the thread's own page.
- Beside BB's side panel, a review from 480 to 600px wide, as at BB's default panel width in a 1440px window, keeps BB's title bar and the band, its commands as icons and its title on one line, where it turned into the phone's layout; on a phone's touch screen, 600px still does. Ask agent in full screen leaves full screen, as BB's panel is outside it, and opening a tab closes Comments over the code. While either chat shows, BB's toasts sit above its message box.
- A phone's dock makes way only while you type in the review, not in BB's panel. Its review id is cut from the end, "web:feat/snooz…", where its middle was cut, and its comments to send count those not on GitHub yet too, as the notice does.
- A review agent's chat deleted while it shows says so, with Start a new chat.
One review from local work through the PR
- A folder's review becomes its PR's within seconds, whoever opens the PR: a thread in the folder that pushes, by
git push,git -C <dir> push,jj git pushorgh stack pushorsubmit, or runsgh pr createhas it checked at once, but while GitHub limits reads, Push finds it when the main thread stops, GitHub is read for every local review in one request every 2 minutes, and an open review asks every 30 seconds. A draft PR, a branch a thread in the folder pushed under another name since the review began (git push origin HEAD:feat/nice,gh pr create --head feat/nice), until a push under its own name again (git push -u origin feat/qa,git push origin HEAD), and a PR opened while the guide is being written now count, where they didn't. A PR older than the review, or from another branch, as a stacked branch's upstream before its first push, "PR #12 is frompart1, not this branch.", waits for Make it PR #12's review or Not this one, after which Review actions (⋯) still offers Make it PR #12's review. - The review keeps its notice, "Now PR #4512's review,
api#4512, with 6 comments carried over, 2 not on GitHub yet. It wasapi:snooze-checks, which still opens it.", with PR #4512 ↗ and Got it, where only a page open as it happened said so. Comments the PR's diff doesn't have are sorted then: onto the PR's lines, Not on GitHub yet where only the folder has the line, and the rest kept on the older diff, "1 is on a line the PR doesn't have, under Needs you.", its Needs you opening Comments there. After a merge it says what moved, and Earlier agent chat ↗ opens the merged review's agent chat beside the review. - Its old id keeps working in every command,
bb review api:snooze-checks,ready,comment,summary,askandapprove; an id that names more than one review not archived, as when that branch has a review of its own now, or the same branch's in two folders, names them back, each with its folder, machine and key, "Use one's key or link.", where it took the newest;bb review api:featopens a review by its id, not as a git ref. - The review agent is told without a new turn: its instructions name the PR and the folder, the next message the review sends it, or its review tools' next answer, says so once, and its thread takes the PR's id.
- A folder's review and the PR's own review merge, where they were linked: at once when the one that goes has nothing of yours, else from Merge into one review, the same on both, whose notice says which stays: "PR #4512 has its own review, with 3 comments and a summary. Merging keeps this one and archives that one.", beside PR #4512's review ↗, or on the PR's review Local review ↗. Keep both stops both offering: the folder's review stays local, and the PR's review stays the PR's; while neither is archived, Review actions (⋯) on either still offers Merge into one review, saying which stays. Comments follow their lines with their ids and Sends, a clashing one into the summary, where a thread's report on it still lands, a tracked one's discussion going on in the summary's, and one not on GitHub yet into your notes, and the summary, notes, Sends and viewed files join. The one merged away is in Archive as "Merged into
api#4512", and its page, link or id opens the review it went into. A 1.8.0 linked pair merges the same way, and a second folder on the branch merges into the first's. - The PR's review keeps its folder: "3 files on MaxBook aren't on GitHub yet." with Review them opens Not pushed yet, now a page after the chapters, "Not pushed yet · 3 files" in the navigator, where it was in the Main thread tab: "3 files on MaxBook aren't on GitHub yet", "Branch
feat/x· compared with PR #9 (c0ffee0)", with Refresh, Viewed kept for each file's revision as the chapters keep it, and at its end "Comments here go with Send, not Submit." with Push and Finish review. A comment on a line only there is marked Not on GitHub yet, its status "Draft · goes with Send", and goes with Send, not Submit, as Finish review says, but never to a fixer at the PR's head or with Fix in a new thread, which haven't its line: "1 isn't on GitHub yet: change Main thread to a thread in its folder to send it.", or, with Send comments to the main thread off, "It stays in the draft: turn on Send comments to the main thread in Settings to send it to a thread in its folder.", and moves to its line in the PR after a push. Comments lists it under Not submitted, whose count is what Submit posts, saying "2 aren't on GitHub yet. They go with Send, not Submit." When the PR has new commits, Update, beside Update guide, takes the PR's head without the guide writer, and the guide says it's older, with Rewrite guide: "The guide was written before the PR’s latest commits." once your Push lands, and "The guide was written for the local changes, before the PR." when the PR's diff isn't the folder's. Open in editor opens the folder's files, on its machine. - Push and open PR, in Finish review, pushes a local review whose branch has no PR as Push does, then has the review agent draft the PR for you to post, as the line above it says, with Push only beside it; Open PR alone is for a branch on GitHub already. Once the draft waits in the agent's chat, Finish says "The PR draft is ready." with Post PR…, which opens the Review agent tab, where it is; a toast says it with the same button when Finish isn't showing. A draft it couldn't ask for says why, with Try again. While the draft waits, or after that, Push shows only while the folder has something new to push. With the agent ...
Code Review Workspace 1.8.1
Reviews in BB's thread list show their names, and checking Viewed keeps your place. Still BB 0.48+ (plugin SDK 0.6.79+) with Node 24+; installs at ^1.0.0 update to 1.8.1. 1.8.1 adds no migration, so rolling back to 1.8.0 keeps everything.
- BB's thread list gives a review's name the whole row. A PR's
#n, or a local review's branch or folder, shows before it only where two rows share a name, where it always did and left the name a few letters. The row's tooltip still says where the review is. - Checking Viewed on a file you're partway through folds it with its row at the top of the view and the next file under it, where the view kept its scroll and landed a file or more further on.
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 Sen...
Code Review Workspace 1.7.0
Save All reviews' filters as named views. Still BB 0.45+ (plugin SDK 0.6.14+) with Node 24+; installs at ^1.0.0 update to 1.7.0. 1.7.0 adds one migration, a filter_views table, on SQLite and on Postgres. Rolling back to 1.6.0 keeps everything, the saved views unused until you update again; on 1.6.0, bb review storage won't move the reviews between SQLite and Postgres, the migration being newer than it.
- Save view keeps All reviews' filters under a name, such as "Live 4 Project" or "Updated this week", in the plugin's database, so they're the same in every browser and on a phone. Views show above the filters as tabs after All; picking one sets its filters, and a date span stays relative to now. Change a view's filters and Save updates it or Save as new names another; Edit view, at the end of the filters, renames or deletes it. Views keep filters only, not the box's words.
- A row starts with its author's GitHub avatar, as the review's header shows it, and a local change with a branch.
- A row shows its PR's GitHub labels at the end of its second line, under its age, each with a dot of its GitHub color: three at most, then
+Nnaming the rest on hover. - A row's size shows its added lines in the diff's green and its removed lines in its red, as
+120 −30 · 8 files, where it was all gray. - A filter's value list taller than the menu cuts its last row in half, so it reads as more to scroll to, where it ended on a whole row and its other values looked missing. A value too long for the menu shows whole on hover.