ultrareview consumed a credit despite crashing before producing any findings
Resolved 💬 1 comment Opened May 30, 2026 by milo-garth Closed Jul 3, 2026
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
- Launched a review via
/ultrareview 616(a GitHub PR in a private repo). - CLI reported:
Free ultrareview 3 of 3.and gave a tracking URL. - The run completed via task-notification, but the only result returned was:
``json``
{"error":"Review crashed before producing findings. See session logs for details."}
- The credit was still consumed — this was my 3rd of 3 free reviews, and a subsequent
/ultrareviewinvocation 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
- Refund the credit consumed by the crashed run.
- Treat "crash before findings" as non-billable going forward.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗