/ultrareview returns "status 404 after 3 attempts" on v2.1.117
Resolved 💬 3 comments Opened Apr 22, 2026 by evpinkunicorn Closed Apr 26, 2026
Environment
- Claude Code version: 2.1.117 (latest, confirmed via
npm view @anthropic-ai/claude-code version) - OS: Windows 11 Home Single Language 10.0.26200
- Shell: bash (Git Bash)
- Plan: Claude Max (stripe_subscription, active)
hasExtraUsageEnabled: truehasSeenUltrareviewTerms: truepassesEligibilityCache.eligible: true,remaining_passes: 3
What happened
Running /ultrareview (no args) in a clean, public GitHub-backed repo fails with:
status 404 after 3 attempts
Repo state (should be fine for ultrareview)
- Repo:
https://github.com/evpinkunicorn/pfc(public, accessible without auth viagit ls-remote) - Branches:
master(full snapshot),main(empty root commit baseline) origin/HEAD→main- Working tree clean, both branches pushed
What I expected
/ultrareview launches cloud multi-agent review of the current branch vs. default baseline.
What I tried
- Confirmed CLI is latest (2.1.117 == npm latest)
- Confirmed subscription is active with passes remaining
- Confirmed repo is public and both branches are on remote
- Retried after a delay — same 404
Hypothesis
Sounds like a server-side issue with the ultrareview endpoint resolving/registering the repo or a transient outage that didn't recover. Happy to provide request IDs if the CLI can surface them.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗