Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /ultrareview crashes silently — opaque "Review crashed" error with no root cause or mitigation [1 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#53777•Fetched 2026-04-28 06:47:30
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
TeroHeinonenTeroHeinonen
Participants
TeroHeinonenTeroHeinonen
Timeline (top)
labeled ×4

/ultrareview <PR#> consistently crashes during the cloud review run and surfaces only an opaque error to the Claude Code CLI:

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

The web session shows an equally-uninformative line:

[heartbeat] 06:44:27
<remote-review>{"error":"Review crashed before producing findings. See session logs for details."}</remote-review>

There is no:

  • specific root cause (timeout? OOM? tool error? rate limit?)
  • file or path that triggered the crash
  • suggested mitigation
  • way to retry from the failed step

Error Message

and surfaces only an opaque error to the Claude Code CLI: {"error":"Review crashed before producing findings. See session logs for details."} <remote-review>{"error":"Review crashed before producing findings. See session logs for details."}</remote-review>

  • specific root cause (timeout? OOM? tool error? rate limit?)
  1. All four crash with the same opaque error. Three were the free

Root Cause

There is no:

  • specific root cause (timeout? OOM? tool error? rate limit?)
  • file or path that triggered the crash
  • suggested mitigation
  • way to retry from the failed step

Fix Action

Fix / Workaround

There is no:

  • specific root cause (timeout? OOM? tool error? rate limit?)

  • file or path that triggered the crash

  • suggested mitigation

  • way to retry from the failed step

  • /ultrareview should complete regardless of PR size, or fail with a clear cause when it cannot.

  • Any failure should surface, in the CLI:

    • specific root cause ("PR diff exceeded N tokens", "tool X timed out at file Y", "rate limited by upstream", etc.)
    • mitigation suggestion ("split into smaller PRs", "retry in M minutes", "run /ultrareview --shallow", etc.)

  • Billed runs that crash before producing findings should not be charged, or should be auto-retried once.

Code Example

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

---

[heartbeat] 06:44:27
<remote-review>{"error":"Review crashed before producing findings. See session logs for details."}</remote-review>
RAW_BUFFERClick to expand / collapse

Summary

/ultrareview <PR#> consistently crashes during the cloud review run and surfaces only an opaque error to the Claude Code CLI:

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

The web session shows an equally-uninformative line:

[heartbeat] 06:44:27
<remote-review>{"error":"Review crashed before producing findings. See session logs for details."}</remote-review>

There is no:

  • specific root cause (timeout? OOM? tool error? rate limit?)
  • file or path that triggered the crash
  • suggested mitigation
  • way to retry from the failed step

Repro

  1. Create a stack of 4 PRs against your own repo. PR 1: ~6 commits, ~80 files (initial scaffold). PR 2: 42 commits. PR 3: 24 commits. PR 4: 14 commits.
  2. Run /ultrareview <N> against each.
  3. All four crash with the same opaque error. Three were the free tier; the fourth was billed as Extra Usage and also crashed — user paid for nothing.

Expected behavior

  • /ultrareview should complete regardless of PR size, or fail with a clear cause when it cannot.
  • Any failure should surface, in the CLI:
    • specific root cause ("PR diff exceeded N tokens", "tool X timed out at file Y", "rate limited by upstream", etc.)
    • mitigation suggestion ("split into smaller PRs", "retry in M minutes", "run /ultrareview --shallow", etc.)
  • Billed runs that crash before producing findings should not be charged, or should be auto-retried once.

Environment

  • Claude Code 2.1.119
  • Linux 6.17.0-20-generic x86_64
  • Repo: private, ~100k LOC
  • Session URLs (for log correlation, available to Anthropic):
    • session_017tzr7T9oYcnSENzsjNxmtD
    • session_01HYSQ37zdsDMMg2DL3U2Yap
    • session_01Mh223mfcVKB3mkaebWj7vM
    • session_01Gz5DPnqz42hy4JEij4MPsZ

extent analysis

TL;DR

The /ultrareview command consistently crashes during cloud review runs, and to move forward, investigating session logs for specific error details is necessary.

Guidance

  • Investigate the session logs for the provided session URLs (e.g., session_017tzr7T9oYcnSENzsjNxmtD) to find more detailed error messages that could indicate the root cause of the crash.
  • Consider reaching out to Anthropic support with the session URLs for further assistance, as they may have access to more detailed logs or insights into the issue.
  • Review the documentation for Claude Code 2.1.119 to see if there are any known issues or limitations with the /ultrareview command, especially regarding large PRs or specific file types.
  • If possible, try running /ultrareview with a smaller PR or a subset of files to see if the issue persists, which could help isolate the problem.

Notes

The lack of specific error details in the provided output makes it challenging to pinpoint the exact cause without access to the session logs or more detailed information about the repository and PRs involved.

Recommendation

Apply workaround: Given the opaque error messages and the absence of a clear root cause, the best immediate step is to investigate the session logs and potentially reach out for support, rather than attempting to apply a specific fix without more information.

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…

FAQ

Expected behavior

  • /ultrareview should complete regardless of PR size, or fail with a clear cause when it cannot.
  • Any failure should surface, in the CLI:
    • specific root cause ("PR diff exceeded N tokens", "tool X timed out at file Y", "rate limited by upstream", etc.)
    • mitigation suggestion ("split into smaller PRs", "retry in M minutes", "run /ultrareview --shallow", etc.)
  • Billed runs that crash before producing findings should not be charged, or should be auto-retried once.
#permission error#memory optimization#batch processing#GPU compatibility#latency issue

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 crashes silently — opaque "Review crashed" error with no root cause or mitigation [1 participants]