[Bug] Ultrareview results not delivered to local session and failed runs consume quota

Status Open
Reported on v2.1.233
Maintainer reply None cached
Activity 1 comment · opened Aug 17, 2026

Bug Description
Title: ultrareview (cloud /code-review ultra) — results never delivered to local session, AND failed runs still consume free-run quota

Defect 1 — Completed review results never reached the session:

Ran /ultrareview 121. The launch banner confirmed it started and gave a tracking URL. The cloud session UI shows the review completed, but:

  1. No task-notification with the findings ever arrived in the local CLI session (the documented delivery mechanism).
  2. Findings were not posted to the GitHub PR (run launched without --post), so there's no fallback copy on the PR.
  3. The cloud session URL is auth-gated — returns 403 to any programmatic fetch — so the results are viewable only in the browser and can't be pulled into the working session. Copy/paste from the browser view is also not working.

Impact: A billed/limited ultrareview run (the last of 3 free runs) completed successfully but its findings are unrecoverable in the environment where the fixes need to be applied.

Defect 2 — Failed runs still consume free-run quota:

In a previous session, /ultrareview was invoked with a wrong/invalid PR number. The run failed (no valid PR to review), yet it still consumed one of the 3 free ultrareview runs. Failed runs — especially ones that fail immediately due to an invalid target — should not count against the free-run allowance.

Expected:

  • Completed ultrareview findings should reliably reach the lo and/or be retrievable after the fact.
  • Runs that fail (invalid PR#, no valid target, or infrastructure failure) should not decrement the free-run quota.

Session: session_01PkucvYDYLC6tqhqm4HRbKH

Environment Info

  • Platform: darwin
  • Terminal: xterm-256color
  • Version: 2.1.233
  • Feedback ID: 72bfe442-f5f2-4afd-a568-25fafaf297c4

Errors

[]

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗