Claude Max + Claude Code rate limits exhausting abnormally fast / possible metering bug

Resolved 💬 12 comments Opened Mar 31, 2026 by AHMEDFOUAAD Closed May 24, 2026

Bug Description
Subject

Claude Max + Claude Code rate limits exhausting abnormally fast / possible metering bug

Message

I’m on a Claude Max plan and I’m seeing abnormal usage/rate-limit behavior in Claude Code that did not happen before.

Environment:

  • Claude Max plan
  • Claude Code versions involved: 2.1.83 through 2.1.88
  • Timezone: Asia/Riyadh
  • OS: Windows

What happened:

  • On 2026-03-31, two separate Claude Code conversations hit rate limits almost immediately.
  • In one of those sessions, /context showed only 32.3k / 1m tokens (3%) and MCP tools were shown as loaded on-demand, but the session still immediately returned:

"You're out of extra usage · resets 2pm (Asia/Riyadh)"

  • A second short/trivial session also immediately returned the same rate_limit behavior.

Important context:

  • I do have an earlier heavier session that used claude-in-chrome__computer repeatedly.
  • In that long session, /context later showed:

mcp__claude-in-chrome__computer using 2.3m tokens (225%) -> save ~450.3k

  • However, that same /context snapshot still showed only about 647.1k / 1m tokens (65%) as active context.
  • That makes it look like the browser-tool warning is cumulative/session-attributed usage, not one live prompt of that size.

Why I think this may be a bug/regression:

  • The two later sessions were fresh/low-context and still rate-limited immediately.
  • This is inconsistent with what the visible context showed. …

Note: Content was truncated.

View original on GitHub ↗

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