Anthropic quietly compressed Claude Code's weekday session limits during peak hours, and the company's own promotion is the quietest admission that something is off.
On March 26, Thariq Shihipar, a member of Anthropic's technical staff working on Claude Code, posted on X that the company was adjusting its five-hour session limits for free, Pro, and Max subscribers during weekdays between 5am and 11am Pacific time — that's 1pm to 7pm Greenwich Mean Time. The reason, in Shihipar's words: "to manage growing demand for Claude." The weekly limits stayed the same. The change landed immediately, with no advance notice.
Anthropic estimated that roughly 7 percent of users would hit session limits they wouldn't have hit before, with Pro-tier subscribers particularly affected. That is not a bug fix. That is a deliberate constraint on a product users are paying up to $200 per month to access.
The backlash was swift and specific. Brad Groux, a Max subscriber, posted on X that Claude Code burned through his entire session allowance while he was working on a single GitHub pull request for regression testing — the meter kept climbing even after he'd closed everything down. A user on the Anthropic Claude Code GitHub repository opened issue #38335 documenting that since March 23, their five-hour session window had been exhausted in one to two hours on identical workloads. A Reddit-compiled timeline of user reports logged more than 2,140 unique reports on Downdetector by mid-afternoon on March 23, the majority citing problems with Claude Chat. During that same window, Anthropic's status page showed all systems operational — a gap users noticed and documented.
On March 13, Anthropic launched a temporary offer running through March 28 that doubles five-hour usage limits during off-peak hours for Free, Pro, Max, and Team subscribers. The promotion is a pressure valve. It is also an implicit acknowledgment that the base tier's limits are tight enough that the company needs to sweeten the deal rather than simply address the underlying constraint. Anthropic did not announce the peak-hour compression alongside it, or at all.
The February prompt caching bug is relevant context for understanding why some users were already frustrated before the March 26 announcement. Anthropic reset rate limits in late February after a bug in prompt caching — the feature meant to reduce costs by reusing context from previous requests — caused usage limits to drain faster than intended. The company hotfixed the bug in version 2.1.62 and reset affected accounts. The five-hour window compression that followed is a separate, intentional change, not a continuation of the caching incident.
Claude Code's Max plan, priced at $100 per month for five times the Pro usage and $200 per month for 20 times the Pro usage, is the tier where the problem bites hardest. These are developers paying $2,400 per year at the high end, running agentic workflows that require sustained session time. Burning through a five-hour window in one to two hours during peak hours is a different problem than burning through it over the full five hours. It means the session limit is now a scheduling constraint, not just a volume constraint.
Community analysts estimated that changes to how Anthropic bills for output tokens at scale produced an effective cost increase of 15 to 40 percent for output-heavy workloads — document processing, long-form generation, agentic pipelines. That figure comes from user calculations on Reddit, not from Anthropic, and it reflects one person's analysis of pricing sheet changes rather than a confirmed measurement. The direction — upward — is consistent with what users are reporting; the specific range should be treated as unverified community math.
Anthropic's own documentation shows that the average Claude Code user costs about $6 per developer per day, with 90 percent of users staying under $12 per day. Those numbers look reasonable in aggregate. They do not account for the workflows that chew through a full session in under two hours, or for what it means to be a Max subscriber hitting peak-hour limits on workflows designed around uninterrupted session time.
The larger pattern is this: Anthropic is managing demand on a product where the subscription tiers are already priced at a premium, without the kind of explicit communication that lets users plan around it. The March 13 promotion acknowledged that off-peak usage is underconstrained. The March 26 peak-hour compression suggests peak usage is overconstrained. Running both policies simultaneously — promotion and limit tightening — is coherent demand management. It is also the kind of move that erodes trust in proportion to how much customers are paying to not think about limits.
What to watch: the March 28 promotion end date. If Anthropic extends the off-peak promotion, it signals the peak-hour compression is a longer-term fixture rather than a temporary response to a spike. If the promotion ends and the compressed limits remain, the message to high-volume subscribers is clear.
