claude-code - 💡(How to fix) Fix [BUG] [ultrareview] Run crashed server-side, consumed free credit (1 of 3) with zero findings produced [2 comments, 3 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#54704Fetched 2026-04-30 06:38:21
View on GitHub
Comments
2
Participants
3
Timeline
13
Reactions
0
Timeline (top)
labeled ×6cross-referenced ×4commented ×2unlabeled ×1

Error Message

/ultrareview was launched against branch v2.1.0main and announced "Free ultrareview 1 of 3". The job ran, was marked completed, but returned no findings — only an error message saying it crashed before producing any. Despite the server-side crash, the free credit was consumed (now showing 1 of 3 used).

Error Messages/Logs

{"error":"Review crashed before producing findings. See session logs for details."} {"error":"Review crashed before producing findings. See session logs for details."}

Code Example

{"error":"Review crashed before producing findings. See session logs for details."}
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

/ultrareview was launched against branch v2.1.0main and announced "Free ultrareview 1 of 3". The job ran, was marked completed, but returned no findings — only an error message saying it crashed before producing any. Despite the server-side crash, the free credit was consumed (now showing 1 of 3 used).

Scope at launch (per command output): 211 files changed, 16,400 insertions, 1,361 deletions.

Tracking session: https://claude.ai/code/session_01FeMucJY998BPVQLv76x8YW Session ID: session_01FeMucJY998BPVQLv76x8YW Date: 2026-04-29 Account: [email protected] Platform: macOS (Darwin 25.3.0)

Requesting refund of the consumed free credit — server-side crashes that produce no output should not count against the free quota.

What Should Happen?

Either: (a) The ultrareview run completes and produces findings, OR (b) If the run crashes server-side before producing any findings, the free credit is not consumed (it should remain at 3 of 3 free reviews available).

Currently the credit is consumed regardless of outcome, which means a crashed run silently costs the user one of their three free credits with zero value delivered.

Error Messages/Logs

{"error":"Review crashed before producing findings. See session logs for details."}

Steps to Reproduce

  1. On a feature branch with a large diff vs main (in my case: 211 files, ~16k insertions, ~1.3k deletions).
  2. Run /ultrareview (no argument — uses current branch vs main).
  3. Command announces "Free ultrareview 1 of 3" and returns a tracking URL.
  4. Wait for the cloud job to finish (~5-10 min expected).
  5. Job is marked completed but returns: {"error":"Review crashed before producing findings. See session logs for details."}
  6. Free credit count is now 1 of 3 used, with no review produced.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.92 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

  • Tracking session URL: https://claude.ai/code/session_01FeMucJY998BPVQLv76x8YW
  • This was the first use of the free ultrareview quota for this account, so I cannot confirm whether the feature ever worked before.
  • The branch had a large diff (~16k insertions) — the crash may correlate with scope size, but the command accepted the launch without warning.
  • Account email: [email protected]
  • Refund request: please return the consumed credit (currently 1/3 used → should be 0/3 since no findings were produced).

extent analysis

TL;DR

The issue can be mitigated by requesting a refund of the consumed free credit and potentially avoiding large diffs until the server-side crash is resolved.

Guidance

  • Review the session logs for details on the crash, as indicated by the error message, to understand the cause of the server-side crash.
  • Verify if the issue is specific to the Opus Claude Model or if it occurs with other models as well.
  • Test the /ultrareview command with a smaller diff to see if the crash is correlated with the scope size.
  • Consider reaching out to the support team for assistance with the refund request and to report the issue.

Notes

The root cause of the server-side crash is unknown, and it is unclear if this is a regression or a new issue. The large diff size may be a contributing factor, but further testing is needed to confirm.

Recommendation

Apply workaround: Request a refund of the consumed free credit and avoid using the /ultrareview command with large diffs until the issue is resolved. This is because the current behavior of consuming a free credit even when the job crashes and produces no findings is undesirable.

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 [BUG] [ultrareview] Run crashed server-side, consumed free credit (1 of 3) with zero findings produced [2 comments, 3 participants]