Documentation Index
Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Ultrareview is a research preview feature available in Claude Code v2.1.86 and later. The feature, pricing, and availability may change based on feedback.
/ultrareview, Claude Code launches a fleet of reviewer agents in a remote sandbox to find bugs in your branch or pull request.
Compared to a local /review, ultrareview offers:
- Higher signal: every reported finding is independently reproduced and verified, so the results focus on real bugs rather than style suggestions
- Broader coverage: many reviewer agents explore the change in parallel, which surfaces issues that a single-pass review can miss
- No local resource use: the review runs entirely in a remote sandbox, so your terminal stays free for other work while it runs
/login and authenticate with Claude.ai first. Ultrareview is not available when using Claude Code with Amazon Bedrock, Google Cloud Vertex AI, or Microsoft Foundry, and it is not available to organizations that have enabled Zero Data Retention.
Run ultrareview from the CLI
Start a review from any git repository in the Claude Code CLI.github.com remote on the repository.
Before launching, Claude Code shows a confirmation dialog with the review scope (including the file and line count when reviewing a branch), your remaining free runs, and the estimated cost. After you confirm, the review continues in the background and you can keep using your session. The command runs only when you invoke it with /ultrareview; Claude does not start an ultrareview on its own.
Pricing and free runs
Ultrareview is a premium feature that bills against extra usage rather than your plan’s included usage.| Plan | Included free runs | After free runs |
|---|---|---|
| Pro | 3 free runs | billed as extra usage |
| Max | 3 free runs | billed as extra usage |
| Team and Enterprise | none | billed as extra usage |
/extra-usage to check or change your current setting.
Track a running review
A review typically takes 5 to 10 minutes. The review runs as a background task, so you can keep working in your session, start other commands, or close the terminal entirely. Use/tasks to see running and completed reviews, open the detail view for a review, or stop a review that is in progress. Stopping a review archives the cloud session, and partial findings are not returned. When the review finishes, the verified findings appear 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.
Run ultrareview non-interactively
Use theclaude ultrareview subcommand to start an ultrareview from CI or a script without an interactive session. The subcommand launches the same review as /ultrareview, blocks until the remote review finishes, prints the findings to stdout, and exits with code 0 on success or 1 on failure.
| Flag | Description |
|---|---|
--json | Print the raw bugs.json payload instead of the formatted findings |
--timeout <minutes> | Maximum minutes to wait for the review to finish. Defaults to 30 |
claude ultrareview requires the same authentication and extra usage configuration as /ultrareview. The subcommand exits with code 0 when the review completes with or without findings, code 1 when the review fails to launch, the remote session errors, or the timeout elapses, and code 130 when interrupted with Ctrl-C. The remote review keeps running if you interrupt the subcommand; follow the session URL printed to stderr to watch it in the browser.
For automatic reviews on GitHub pull requests, Code Review integrates with your repository directly and posts findings as inline PR comments without a CLI step.
How ultrareview compares to /review
Both commands review code, but they target different stages of your workflow./review | /ultrareview | |
|---|---|---|
| Runs | locally in your session | remotely in a cloud sandbox |
| Depth | single-pass review | multi-agent fleet with independent verification |
| Duration | seconds to a few minutes | roughly 5 to 10 minutes |
| Cost | counts toward normal usage | free runs, then roughly $5 to $20 per review as extra usage |
| Best for | quick feedback while iterating | pre-merge confidence on substantial changes |
/review for fast feedback as you work. Use /ultrareview before merging a substantial change when you want a deeper pass that catches issues a single review might miss.
Related resources
- Claude Code on the web: learn how remote sessions and cloud sandboxes work
- Plan complex changes with ultraplan: the planning counterpart to ultrareview for upfront design work
- Manage costs effectively: track usage and set spending limits