Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix ultrareview consumed a credit despite crashing before producing any findings

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…

A cloud /ultrareview run crashed before producing any findings, but still consumed one of my free ultrareview credits. A run that returns zero output should not be billed.

Error Message

{"error":"Review crashed before producing findings. See session logs for details."} The credit was consumed for a run that produced no findings — only the crash error above.

  • Error returned: Review crashed before producing findings. See session logs for details.

Root Cause

A cloud /ultrareview run crashed before producing any findings, but still consumed one of my free ultrareview credits. A run that returns zero output should not be billed.

Code Example

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

Summary

A cloud /ultrareview run crashed before producing any findings, but still consumed one of my free ultrareview credits. A run that returns zero output should not be billed.

What happened

  1. Launched a review via /ultrareview 616 (a GitHub PR in a private repo).

  2. CLI reported: Free ultrareview 3 of 3. and gave a tracking URL.

  3. The run completed via task-notification, but the only result returned was:

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

  4. The credit was still consumed — this was my 3rd of 3 free reviews, and a subsequent /ultrareview invocation indicated no free reviews remained.

Expected behavior

If a cloud review crashes before producing any findings, the credit should not be consumed (or should be automatically refunded).

Actual behavior

The credit was consumed for a run that produced no findings — only the crash error above.

Details for investigation

  • Crashed session ID: session_012Jv4ZMkdbarmsK67eiixkw
  • Error returned: Review crashed before producing findings. See session logs for details.
  • Command: /ultrareview <PR#> (cloud-based code review)

Environment

  • Claude Code version: 2.1.158
  • OS: macOS 26.3 (Darwin 25.3.0)
  • Platform: darwin / arm64

Ask

  1. Refund the credit consumed by the crashed run.
  2. Treat "crash before findings" as non-billable going forward.

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 a cloud review crashes before producing any findings, the credit should not be consumed (or should be automatically 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 ultrareview consumed a credit despite crashing before producing any findings