[Bug] Rate limit error despite available quota on Pro plan

Resolved 💬 3 comments Opened Mar 30, 2026 by linchichuan Closed Apr 2, 2026

Bug Description
Bug: "Rate limit reached" error despite available usage quota (Pro plan)
I'm on the Claude Pro plan and consistently getting API Error: Rate limit reached even though my /usage shows significant capacity remaining (around 30–70%).
Steps to reproduce:

Open Claude Code in terminal (Ghostty)
Ask a few questions
Get "Rate limit reached" error
Check /usage — it shows quota is NOT exhausted
Even after fully shutting down and restarting the computer, the error persists on the next session

Expected behavior: If /usage shows remaining quota, I should be able to continue using Claude Code without hitting a rate limit.
Actual behavior: Rate limit error appears regardless of available quota, and the issue survives a full machine restart — suggesting it's server-side, not a local session state issue.
Environment: macOS, Ghostty terminal, Claude Pro plan

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.1.87
  • Feedback ID: c71a26c6-0a08-4283-b703-c7586b1d84d4

Errors

[{"error":"Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"Extra usage is required for long context requests.\"},\"request_id\":\"req_011CZYrPXiw181dPBwpqyGLv\"}\n    at generate (/$bunfs/root/src/entrypoints/cli.js:11:51105)\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:5435)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-30T07:14:44.697Z"}]

View original on GitHub ↗

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