Subject: BUG: Persistent 429 Rate Limit Error / Stuck Stop Hooks on Claude Max Plan Message

Resolved 💬 5 comments Opened Feb 28, 2026 by a22-00 Closed Mar 29, 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?

Hello, I am on the Claude Max subscription plan and my Claude Code CLI is completely locked out due to a persistent "API Error: Rate limit reached" and hanging on "running stop hooks...". It has been over 12 hours, meaning my per-minute and daily TPM/RPM quotas have naturally reset, yet the CLI still throws the error immediately upon launch. I have already completed all local troubleshooting: Waited 12+ hours to clear TPM/RPM limits. Terminated all background processes (pkill claude). Deleted the local project .claude cache. Wiped global auth tokens and ran a fresh claude login. Updated the CLI to the newest version. Ensured I am not routing through a VPN that might trigger an IP-based block. Because local state has been wiped, this appears to be a backend desync where my account is erroneously flagged or stuck in a rate-limited state. Please escalate this to an engineer to reset my account's API quota state manually.

What Should Happen?

It should be allowing access to Claude Code but it keeps giving an error message: "API Error: Rate limit reached."

Error Messages/Logs

API Error: Rate limit reached

Steps to Reproduce

  1. Open Claude Code
  2. Enter a message or prompt

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.63

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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