[BUG] Claude Code Terminal - API Error: Rate limit reached despite low usage (Pro account)

Resolved 💬 3 comments Opened Mar 30, 2026 by nathaubam Closed May 15, 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 request in Claude Code terminal (CMD on Windows) immediately returns 'API Error: Rate limit reached', despite very low usage (4% session, 18% weekly). The Claude Code VS Code extension works perfectly fine on the same account and machine. I previously used my session token (extracted via Claude Code CLI) in a third-party app called OpenClaw running in Docker. I have since removed OpenClaw and the Docker container, performed /logout and /login in Claude Code terminal to regenerate a new session token, and deleted the .credentials file — but the issue persists. This suggests the account is in an inconsistent state server-side

What Should Happen?

Claude Code terminal should successfully send requests to the API using my Claude Pro account session, without returning 'API Error: Rate limit reached', given that my current usage is only 4% of the session limit and 18% of the weekly limit.

Error Messages/Logs

Steps to Reproduce

  1. Open CMD on Windows
  2. Run claude to launch Claude Code terminal
  3. Type any message (e.g. "test")
  4. Immediately receives 'API Error: Rate limit reached'
  5. Run /status → shows 4% session usage, 18% weekly usage, Login method: Claude Pro Account
  6. Run claude config list → no ANTHROPIC_API_KEY or abnormal config found
  7. Error persists after /logout + /login and after deleting .credentials file

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.87 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

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