Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /ultrareview crashes twice on same PR — "Review crashed before producing 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…

/ultrareview <PR#> crashed twice in a row on the same target PR, consuming 2 of 3 free reviews with zero findings delivered. Both attempts returned the identical opaque error.

Error Message

/ultrareview <PR#> crashed twice in a row on the same target PR, consuming 2 of 3 free reviews with zero findings delivered. Both attempts returned the identical opaque error. {"error":"Review crashed before producing findings. See session logs for details."}

  • Invocation 1: /ultrareview origin/develop — rejected by the local CLI as not-a-valid-branch (separate, minor UX issue — origin/<branch> should either be accepted or the error should suggest the bare-branch form)
  1. Surface the underlying error in the task-notification payload (or the tracking URL) instead of "See session logs for details" — users have no way to access session logs from the CLI.

Root Cause

/ultrareview <PR#> crashed twice in a row on the same target PR, consuming 2 of 3 free reviews with zero findings delivered. Both attempts returned the identical opaque error.

Code Example

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

Summary

/ultrareview <PR#> crashed twice in a row on the same target PR, consuming 2 of 3 free reviews with zero findings delivered. Both attempts returned the identical opaque error.

Sessions to investigate

  • session_013KSjLYXJiXrU55LsjTZqHq
  • session_019eUQ5uYQj2WKg5h2q3rzBw

Both completed (status: completed) but the task-notification payload was:

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

Reproduction

  • Target: a GitHub PR
  • Diff size: 51 files changed, +2937 / -1126 (might be relevant if there's a payload-size threshold)
  • Invocation 1: /ultrareview origin/develop — rejected by the local CLI as not-a-valid-branch (separate, minor UX issue — origin/<branch> should either be accepted or the error should suggest the bare-branch form)
  • Invocation 2: /ultrareview 557 — ran in the cloud, crashed
  • Invocation 3: /ultrareview 557 again — same crash

Asks

  1. Refund the 2 free reviews that produced no output.
  2. Surface the underlying error in the task-notification payload (or the tracking URL) instead of "See session logs for details" — users have no way to access session logs from the CLI.
  3. Pre-flight the crash condition if it's deterministic (e.g., diff too large, missing base-ref, auth issue). Better to fail fast at invocation time than burn quota on a guaranteed crash.

Environment

  • Claude Code CLI
  • Branch was active and well-formed (verified by user via gh pr view)
  • Tests passing, lint clean — the PR itself wasn't malformed

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…
#chain error#conversation history#tool integration#LLM response#prompt template

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 crashes twice on same PR — "Review crashed before producing findings"