You've hit your session limit · resets 11:50am (Europe/Budapest)

Status Open
Reported on v2.1.234
Maintainer reply None cached
Activity 2 comments · opened Aug 18, 2026

Bug Description
Claude Code usage metering issue starting August 17, 2026.

I'm on a Claude Team plan (I'm on a Claude Team plan.).

Until August 17, I used Claude Code extensively every day, including long sessions with >150K context, and I very rarely reached my 5-hour session limit.

Starting August 17, this behavior changed suddenly. My 5-hour Current Session allowance can now go from available to 100% used in approximately 10 minutes of normal Claude Code work.

My workflow, projects and typical context sizes have not materially changed.

Current /usage data:

  • Session (5h): 100%
  • Weekly (7 day): 33%
  • Weekly Fable: 64%
  • 100% of usage in the last 24h was at >150K context

I understand that >150K context is more expensive. However, I regularly worked with similarly large contexts before August 17 without exhausting the 5-hour allowance this quickly.

The timing also coincides with the resolved Claude Code incident on August 17 (13:56–15:29 UTC).

Please investigate whether there was a change or issue with server-side usage metering, prompt caching, long-context accounting, or Claude Code behavior around August 17.

In particular, I would like the team to check the server-side usage charged to my 5-hour sessions and determine which requests caused the session allowance to reach 100% so quickly.

This is a sudden, reproducible change in behavior, not a general question about how usage limits work.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.234
  • Feedback ID: 4d3a6b8e-e240-42ff-8e14-8f46031b4c8a

Errors

[]

View original on GitHub ↗

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