claude-code - 💡(How to fix) Fix [BUG] Ultrareview crashed twice before producing findings — 2 free credits consumed [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#55108Fetched 2026-05-01 05:46:04
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×6commented ×1

Error Message

both returned: {"error":"Review crashed before producing findings. See session

Error Messages/Logs

{"error":"Review crashed before producing findings. See session logs for 5. After ~5-10 min, returns crash error with no findings

Code Example

{"error":"Review crashed before producing findings. See session logs for      
  details."}                                                              
                                                                                
  Session 1: https://claude.ai/code/session_01CPHFQcajjvA9P1m6xV5Q18
  Session 2: https://claude.ai/code/session_019wUz4zTTSnunJYmkjj4qkR
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 crashes before producing any findings. Two consecutive sessions
both returned: {"error":"Review crashed before producing findings. See session logs for details."}

What Should Happen?

Ultrareview should complete the review and return findings, or at minimum not consume a free credit if it crashes.

Error Messages/Logs

{"error":"Review crashed before producing findings. See session logs for      
  details."}                                                              
                                                                                
  Session 1: https://claude.ai/code/session_01CPHFQcajjvA9P1m6xV5Q18
  Session 2: https://claude.ai/code/session_019wUz4zTTSnunJYmkjj4qkR

Steps to Reproduce

  1. Set up a local git repo with master branch containing code (106 files including binary .mp3/.png assets)
  2. Create an empty main branch as base
  3. Run /ultrareview (no args) from master branch
  4. Session launches, shows "Scope: 106 files changed, 31698 insertions"
  5. After ~5-10 min, returns crash error with no findings

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.123

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

The repo includes binary files (.mp3, .png) which may be causing the crash during analysis. Requesting credit refund for both crashed sessions (credits 1 and 2 of 3 free uses consumed).

extent analysis

TL;DR

The Ultrareview crash may be caused by the presence of binary files in the repository, and excluding them from the review might resolve the issue.

Guidance

  • Verify if the issue persists when running Ultrareview on a repository without binary files (.mp3, .png) to isolate the cause.
  • Check the session logs for more detailed error messages that might indicate the specific reason for the crash.
  • Consider excluding binary files from the review process using available configuration options, if any.
  • Test the review process with a smaller set of files to see if the issue is related to the number of files being analyzed.

Example

No code snippet is provided as the issue does not imply a specific code-related fix.

Notes

The presence of binary files in the repository is suspected to be the cause of the crash, but without more detailed logs or error messages, it's difficult to provide a definitive solution. The guidance provided is based on the information given and may need to be adjusted based on further investigation.

Recommendation

Apply workaround: Exclude binary files from the review process, if possible, to see if it resolves the issue. This is recommended because the presence of binary files is suspected to be the cause of the crash, and excluding them might allow the review to complete successfully.

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