Claude Code /ultrareview - Cloud code review using a fleet of parallel agents
by•
Ultrareview runs parallel reviewer agents on your branch or PR in a remote cloud sandbox, independently verifying each bug before reporting it.
For Claude Code users on Pro or Max plans.
Replies
A single-pass code review, automated or manual, can only catch what one pass catches. Ultrareview takes a different approach.
It is a /ultrareview command for Claude Code that spins up a fleet of reviewer agents in a remote cloud sandbox, runs them in parallel across your diff, and independently verifies each finding before reporting it. The result is a short list of confirmed bugs rather than a long list of suggestions to triage.
The workflow is non-blocking by design. You confirm the review scope in a dialog, the agents run in the background, and findings come back as a notification in your CLI session when complete. Typically 10 to 20 minutes. You can close the terminal and it keeps running.
Key features:
Multi-agent parallel exploration of the diff
Independent reproduction step cuts false positives before findings land
Remote sandbox keeps your local session free during the review
PR mode pulls directly from GitHub, no local bundling required
Each finding includes file location and fix context
Who it's for: Claude Code users on Pro or Max plans, specifically before merging substantial changes where a missed bug is expensive. Auth flows, schema migrations, critical refactors.
Research preview, available in Claude Code v2.1.86 and later. Pro and Max users each get 3 free runs to try it.
P.S. I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified → @rohanrecommends
@rohanrecommends For someone shipping B2B tools with heavy workshop integrations (think 50+ connected schemas across frontend/backend), how does Ultrareview handle cross-file dependency chains? Like if Agent A flags a schema migration issue, does Agent B automatically verify the downstream API impacts, or do you get siloed findings that need manual stitching?
@rohanrecommends How does it handle verifying fixes in iterative PRs, like confirming a patch resolves the finding? Tried it on auth flows yet?
been doing this manually — agent reviews, second agent verifies its findings, sometimes a third when something looks uncertain. you get closer to correct, but you're rebuilding the same scaffolding on every pr. does it actually catch what the third pass was catching?
This could significantly speed up PR cycle it false positives stay low.
Wannabe Stark
Worth every penny
How does /utrareview handle reviewing integration issues? does it require any documentation on CI/CD setup and external dependencies?
parallel reviewer agents in a sandbox that independently verify before flagging is a nice take on hallucination control. one question — how do you dedupe when two agents surface the same bug with slightly different framings? always a pain with multi-agent review.