claude-code - 💡(How to fix) Fix /ultrareview returns "status 404 after 3 attempts" on v2.1.117 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#51965Fetched 2026-04-23 07:40:11
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×1cross-referenced ×1

Code Example

status 404 after 3 attempts
RAW_BUFFERClick to expand / collapse

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: true
  • hasSeenUltrareviewTerms: true
  • passesEligibilityCache.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 via git ls-remote)
  • Branches: master (full snapshot), main (empty root commit baseline)
  • origin/HEADmain
  • 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.

extent analysis

TL;DR

The issue is likely due to a server-side problem with the ultrareview endpoint, and providing request IDs may help diagnose the issue.

Guidance

  • Verify that the ultrareview endpoint is functioning correctly by checking the status of the Claude Code service.
  • Check if there are any known issues or outages reported by the Claude Code team that may be affecting the ultrareview endpoint.
  • If possible, try running the /ultrareview command with the --verbose flag to gather more detailed output that may help identify the issue.
  • Consider providing the request IDs to the Claude Code support team to help them investigate the issue.

Notes

The issue seems to be related to a server-side problem, and without more information about the Claude Code service or the ultrareview endpoint, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Provide request IDs to the Claude Code support team to help them investigate the issue, as this may help resolve the problem or provide more insight into the cause.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix /ultrareview returns "status 404 after 3 attempts" on v2.1.117 [1 comments, 2 participants]