What
- The failure message shown when a cloud
/code-reviewrun fails no longer always tells the user to retry/code-review ultraor fall back to local review. It now branches on the specific failure reason, such assession_archived,stopped_remotely, orsession_not_found, only recommending the ultra/local retry for a subset of causes. - Whether a poll that repeatedly gets 404s is treated as
session_not_foundversus just a timeout is now controlled by a remote-config flag,tengu_breezy_diffie.
Why
This gives clearer, more accurate next steps when a cloud code review fails, instead of always pointing to the same generic retry advice regardless of the actual cause.
Names in the bundle/code-review ultra
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Code Review touched a line naming /code-review ultra after this was published.
Ultrareview requires authentication with a claude.ai account and is not available on Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry, or to organizations with Zero Data Retention enabled or with the [HIPAA configuration…code-review see the edit
Confirmed since
Anthropic's documentation has since written up /code-review ultra, on Find bugs with ultrareview.
`claude -p '/code-review ultra'` doesn't get you the findings, so use `claude ultrareview` in scripts. The `-p` run launches the cloud review and exits without waiting for it. When the review would bill usage credits, the `-p` run stops wi…ultrareview see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /code-review ultra, on Find bugs with ultrareview.