[BUG] /ultrareview consumes a free trial when the run fails with a server-side rate limit

Resolved 💬 3 comments Opened Jun 1, 2026 by myrnf Closed Jul 5, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Summary

Triggered /ultrareview on my branch. The remote agent errored with a
server-side rate-limit message (explicitly "not your usage limit"), but
the failed run was counted against my free-trial quota. Retrying says
"1 of 3 free tries used up."

Actual

  • Run failed with: `API Error: Server is temporarily limiting requests

(not your usage limit) · Rate limited`

  • Findings returned: empty array (likely the run never wrote results)
  • Trial counter incremented to 1/3 anyway

What Should Happen?

Expected

A run that fails due to Anthropic server throttling should not consume
a free trial credit.

Error Messages/Logs

Steps to Reproduce

Repro context

  • Command: /ultrareview (no arg, against local branch)
  • Branch: phase-4-performance → main
  • Scope reported pre-run: 108 files changed, ~21k insertions
  • Approximate time: 2026-06-01 12:49:03 +04
  • Session URL from the CLI output: <paste the claude.ai/code/session_... link>

## Ask
Please refund the consumed trial credit and surface this case to whichever
team owns the trial-quota bookkeeping — the failure was clearly server-side
(per the error string itself), not user behavior.

## Screenshot
<img width="1483" height="174" alt="Image" src="https://github.com/user-attachments/assets/dacf3938-702e-4266-88d5-2c6225dc1291" />

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude Code 2.1.150

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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