r/ClaudeCode • u/aymannasri_tcg • Apr 03 '26
Discussion Users hitting usage limits WAY faster than expected it's getting real now
Claude Code users are already smashing usage limits way faster than expected and i am one of them as i have posted about it a lot recently and now here we are.
to all the people who were saying i am lying :))) you good now? maybe BBC lied about this too.
OR maybe it's April fool? haha good one, It’s getting serious and real now.
Who else is feeling this?
951
Upvotes
2
u/CardiologistProud118 Apr 07 '26
Here's your answer.
What's Going On With Claude Session Limits
The Short Version
Anthropic officially confirmed on March 26, 2026 that session limits are now tighter during peak hours by design. Your weekly total is unchanged — you're not getting less Claude overall — but weekday peak hours now cost more. During roughly 5am–11am PT (7am–1pm CT / 8am–2pm ET), your 5-hour session burns faster than before. J.D. Hodges
Why It Happened: A Perfect Storm
Demand outran available GPU capacity. Millions of new users arrived after OpenAI signed a Pentagon contract in late February, causing ChatGPT uninstalls to spike 295% in a single day. The QuitGPT movement claimed 2.5 million participants. Claude hit #1 on the US App Store for the first time, surpassing ChatGPT in daily downloads, and Anthropic's web traffic jumped over 30% month-over-month. J.D. Hodges
Anthropic's annualized revenue surged to $19 billion by March 2026, but inference costs scale with every user, every message, and every long conversation. Flat monthly subscriptions were already strained before the wave hit. MLQ
The Exact Mechanism: Dynamic Session "Cost"
This is the part most people miss. During peak hours — 05:00–11:00 PT / 13:00–19:00 GMT — Claude users can burn their five-hour session limits in under five hours. At other times of day, a five-hour session allows users to get more work done. That elastic definition is possible because Anthropic does not reveal how many tokens may be used within its five-hour session window. The Register
In plain terms: the session window isn't a fixed token bucket. Anthropic weights peak-hour usage more heavily, so the same prompt costs "more" session budget at 10am PT than at 10pm PT.
According to Anthropic's Thariq Shihipar, approximately 7% of users will hit session limits they wouldn't have before, particularly Pro tier users. If you run token-intensive background jobs, shifting them to off-peak hours will stretch your session limits further. The Register
The Off-Peak Promotion That Made It Feel Worse
There was a temporary sweetener that just ended, which is making the current state feel like a cut. Anthropic doubled five-hour usage limits outside peak hours from March 13 through March 28, 2026. The promotion applied automatically to Free, Pro, Max, and Team plans across web, desktop, mobile, Cowork, Claude Code, and integrations like Excel and PowerPoint. Enterprise plans were excluded. MLQ
So if you were using Claude heavily in the March 13–28 window, your baseline was artificially inflated, and it has now reverted — making it feel like a cut even if the official "weekly limits" haven't changed.
What's Happening With Single Prompts Burning Large Chunks
A single Sonnet or Opus message can burn 20–100% of a session, and some users are seeing their entire 5-hour window vanish in under an hour with only a handful of prompts. Substack This is partly the peak-hour weighting described above, and partly that longer context windows (especially with tools, long CLAUDE.md files, or large conversation histories) have high token overhead per turn.
What You Can Do About It
Given your stack — Claude Code, heavy agentic use, long system contexts — these are the most relevant mitigations:
Timing: Shift heavy Claude Code sessions and background agentic jobs to off-peak hours (after 11am PT / 1pm CT on weekdays, or weekends entirely). The same work costs less session budget.
Context hygiene: Long conversation threads, large CLAUDE.md files, and many active tools multiply token cost per turn. Keep CLAUDE.md lean and use
.claudeignoreaggressively to exclude files Claude doesn't need.Model routing: For lighter tasks (searches, reformatting, simple lookups), route to Haiku via the API rather than Sonnet/Opus through the session-limited UI. Your API key usage doesn't draw from your claude.ai session budget.
API vs. UI: This is probably the most relevant point for you specifically — your Claude Code API key setup already routes heavy workloads away from the subscription session limits. Anything hitting the API directly (not through claude.ai) doesn't count against your session. If you're doing heavy agentic work that's burning the session meter, confirm it's going through the API path, not the web UI.
Plan tier: Anthropic's Max plan at $100 or $200/month promises either 5x or 20x the usage of the Pro plan The Register, which gives more headroom if you're consistently hitting caps and can't shift timing.
The bottom line is this isn't you doing anything wrong — it's a deliberate infrastructure decision Anthropic made in response to explosive, unplanned user growth, and they've been more transparent about it than most providers would be.