claude-code - 💡(How to fix) Fix C:/Program Files/Git/ultrareview crashes consume free runs without producing results [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#56090Fetched 2026-05-05 05:58:29
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×5commented ×1cross-referenced ×1

Running /ultrareview (no-arg form, local branch vs main) results in a crash before producing any findings, but the free run is still consumed.

Error Message

  1. Receive notification: {"error":"Review crashed before producing findings. See session logs for details."} Two consecutive /ultrareview attempts both crashed with the same error, and both consumed free runs (reducing the allocation from 3 to 1, then to 0).

Error message received

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

Root Cause

Request

Please investigate the crash root cause and consider refunding the 2 consumed free runs (account: 88milion / [email protected]).

Code Example

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

Bug Report

Description

Running /ultrareview (no-arg form, local branch vs main) results in a crash before producing any findings, but the free run is still consumed.

Steps to reproduce

  1. Run /ultrareview in a git repository with a non-trivial branch
  2. Wait ~5-10 minutes for the remote agent to complete
  3. Receive notification: {"error":"Review crashed before producing findings. See session logs for details."}
  4. Free run count is decremented despite no output

Expected behavior

If the review crashes before producing findings, the free run should not be consumed (or should be refunded).

Actual behavior

Two consecutive /ultrareview attempts both crashed with the same error, and both consumed free runs (reducing the allocation from 3 to 1, then to 0).

Error message received

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

Sessions

  • Session 1: crashed before producing findings
  • Session 2: crashed before producing findings (second consecutive crash)

Environment

  • Claude Code CLI on Windows 11 Pro
  • Repository: private project, branch claude-devmain
  • Diff scope reported: 159 files changed, 18075 insertions(+), 535 deletions(-)

Request

Please investigate the crash root cause and consider refunding the 2 consumed free runs (account: 88milion / [email protected]).

extent analysis

TL;DR

The issue can be mitigated by investigating the session logs for details on the crash and potentially refunding the consumed free runs.

Guidance

  • Investigate the session logs to determine the root cause of the crash, as suggested by the error message.
  • Verify that the free run count is correctly updated when a review crashes before producing findings.
  • Consider reaching out to support to request a refund of the consumed free runs, providing the account information and details of the crashes.
  • Check if there are any known issues or updates related to the Claude Code CLI on Windows 11 Pro that may be contributing to the crash.

Notes

The exact cause of the crash is unknown without further investigation of the session logs, and the solution may depend on the specific details of the error.

Recommendation

Apply workaround: Refund the consumed free runs, as the review crashed before producing findings and the free run count was decremented incorrectly.

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

If the review crashes before producing findings, the free run should not be consumed (or should be refunded).

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 C:/Program Files/Git/ultrareview crashes consume free runs without producing results [1 comments, 2 participants]