claude-code - 💡(How to fix) Fix [ultrareview] Two consecutive crashes on large diff — free credits consumed without findings

Summary

/ultrareview crashed twice in a row on the same branch without producing any findings, but both attempts decremented my free credit counter (now at 0/3 with no actionable output).

Crashed sessions

Repro context

• Branch: main
• Scope reported by CLI: 4 files changed, 7145 insertions(+), 107 deletions(-)
• Largest file in diff: public/style.css (~25k lines total, ~2500 lines added across the diff)
• Project: vanilla HTML/CSS/JS Kanban app (no React, no build step)
• Branch state: clean working tree before launch, both attempts launched within minutes of each other

What I expected

A multi-agent cloud review producing findings (or at minimum an actionable error message + a non-charged credit when the review fails internally).

What happened

Same opaque crash twice, both billed against my free quota. The error message points to "session logs" that are not visible to me, so I cannot self-diagnose.

Hypothesis

Either (a) the diff exceeds an internal context budget on the reviewer sub-agent and there is no graceful fallback, or (b) a transient infra issue that didn't recover on retry. In both cases, charging the user for a crashed run seems unintended.

Request

1. Refund both free credits (`r61isfvfh` and `r54lzf35u`) — current counter shows 0/3 remaining but I got zero findings.
2. Confirm the failure mode so I know whether to scope future runs to smaller diffs (single-file PRs) to avoid hitting the same wall.
3. Improve the error surface: when the reviewer crashes, the CLI should either (a) not consume a credit, or (b) return something more actionable than "see session logs" (which the user cannot access).

Environment

• Claude Code CLI on Windows 11 Pro (10.0.26200)
• Shell: bash (Git for Windows)
• Model: claude-opus-4-7 (1M context)
• Working dir: a single-package vanilla JS project, no monorepo