Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
One change · claude-code

Find bugs with ultrareview changed

ultrareview

Nearest release: v2.1.280, published 10 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 23 Sep 2026 01:48 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 23 Sep 2026 02:07 UTC.

Upstream edited
Recorded here
Lines+8added
Lines−2removed
From line 137 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits9to this page, all time

The whole hunk

from line 137, old and new numbered
/
lines
from line 137
137137 
138138Use `/tasks` to see running and completed reviews, open the detail view for a review, or stop a review that is in progress. If you stop a review, Claude Code archives the cloud session and doesn't return partial findings.
139139 
140Claude can also tell you that a review was stopped or that its session wasn't found:
141 
142* If the review's cloud session is stopped or [archived](/docs/en/claude-code-on-the-web#archive-sessions) on claude.ai before the review finishes, Claude tells you it was stopped.
143* If the review's cloud session was deleted, or you've signed in to a different Claude account or organization since launching it, Claude tells you the session wasn't found.
144* If you switched accounts, the review may still finish under the account that started it. If the review is still running, sign back in as that account and resume the conversation with `claude --resume` to re-attach it.
145 
140146When the review finishes, Claude Code shows the verified findings as a notification in your session. Each finding includes the file location and an explanation of the issue so you can ask Claude to fix it directly.
141147 
142148## Run ultrareview non-interactively
from line 175
169175The subcommand exits with one of three codes:
170176 
171177* **0**: the review completed, with or without findings
172* **1**: the review failed to launch, the cloud session errored, or the timeout elapsed
178* **1**: the review failed to launch or was stopped before it finished, the cloud session errored, or the timeout elapsed
173179* **130**: you interrupted the subcommand with Ctrl-C
174180 
175181If you interrupt the subcommand, the remote review keeps running; follow the session URL printed to stderr to watch it in the browser.
from line 182
176182 
177183With `--post`, the subcommand starts the post right after printing the findings, and prints the link to stderr.
178184 
179* If the run fails, times out, or you interrupt it, the subcommand posts nothing.
185* If the run fails, is stopped, or times out, or if you interrupt it, the subcommand posts nothing.
180186* If the review completes but the comment isn't posted, Claude Code prints the reason to stderr, and the findings stay on stdout so you can post them by hand.
181187 
182188For automatic reviews on GitHub pull requests, [Code Review](/docs/en/code-review) integrates with your repository directly and posts findings as inline PR comments without a CLI step.
Feedback