/ultrareview crashed without findings, consumed 1 of 3 free quota

Resolved 💬 3 comments Opened May 9, 2026 by lm1273 Closed May 9, 2026

Bug: /ultrareview crashed silently, free quota decremented

Date: 2026-05-09
Session ID: session_01LWcnLE9Uswic4FBKkpVeu5
Scope: Large branch (~38k insertions, ~290 files, ~150 commits)
Free tier: consumed 1 of 3 free ultrareviews

Symptom

Ran /ultrareview (no args, defaults to local branch vs master). The CLI launched successfully and reported:

Free ultrareview 1 of 3. Ultrareview launched for <branch> → master (~5-10 min, runs in the cloud). Scope: 291 files changed, 37953 insertions(+), 234 deletions(-)

After ~5-10 minutes, received a task-notification with status=completed. The findings payload was:

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

The free-tier counter decremented despite producing zero output. Immediately afterward I also got an API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited from the CLI session, which may or may not be related.

Expected behavior

A crashed review should either:

  1. Not count against the free-tier quota, or
  2. Surface the error before quota is consumed (with a clear retry path).

Repro context

  • Single feature branch with multiple sequential sub-plans merged into it (large but coherent diff)
  • All CI checks green at HEAD before invoking /ultrareview
  • Branch passes local typecheck + tests + lint + build

Request

  • Please investigate session logs for session_01LWcnLE9Uswic4FBKkpVeu5 to find the root cause.
  • If the crash was infrastructure-side (not user input), please consider restoring the consumed quota (1 attempt back to the free tier).
  • Consider a retry-on-crash mechanism for paid attempts so users aren't billed for crashes.

Happy to provide more context (logs, repo details) privately on request — just let me know the right channel.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗