Rate limit blocks even /logout and basic commands despite 0% usage shown

Resolved 💬 1 comment Opened Apr 16, 2026 by digiuseppedomenicoESH Closed May 25, 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?

Every command inside Claude Code immediately returns "API Error: Rate limit reached",
including non-inference commands like /logout, /status, and config.
The Usage tab shows 0% consumption. The rate limit fires before any actual work is done.

What Should Happen?

Non-inference commands like logout should never be blocked by rate limits.
A 0% usage reading should mean no rate limiting is active.

Error Messages/Logs

API Error: Rate limit reached

Steps to Reproduce

  1. Open Claude Code in terminal (claude)
  2. Type any command: /logout, /status, or config
  3. Immediately receive "API Error: Rate limit reached"
  4. Check /status → Usage tab → shows 0%

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

2.1.59

Claude Code Version

2.1.59

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

  • ANTHROPIC_API_KEY not set
  • Two subscriptions active on the account
  • Previously had duplicate installations (npm residue + native), now cleaned up
  • Related issue: #41084

View original on GitHub ↗

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