Detailed Analysis
A Claude Pro plan user posting to the r/ClaudeAI subreddit reports a marked acceleration in hitting daily usage limits beginning in late April or early May 2026, describing a workflow that previously sustained multiple complex, long-horizon coding and conversational sessions but now exhausts allowances within approximately 30 minutes. The user's setup involves concurrent usage of Claude Code and the Claude web interface, primarily running Opus 4.7, with supplemental use of Sonnet and Google's Gemini Pro as overflow models. Despite actively reducing the Claude Code "effort" setting from "xhigh" through "high" to "medium" — a parameter that governs how deeply the agentic system reasons and iterates on tasks — the token consumption rate remained largely unchanged, suggesting that either the underlying compute behavior did not scale proportionally to the setting, or that Anthropic's limit-enforcement mechanisms shifted independently of user-side configuration.
The specific token figures cited are notable: a single conversation consuming approximately 350,000 tokens and a second consuming 60,000 tokens, together triggering a rate limit within a single morning session. These numbers illustrate the exponential token demands of agentic coding workflows, where Claude Code's agentic loop generates not only user-visible outputs but also internal planning steps, tool call scaffolding, and multi-turn self-correction cycles. Opus 4.7, as Anthropic's most capable and computationally expensive model tier, amplifies this consumption relative to Sonnet or Haiku, meaning the user's model preference compounds the structural token-intensiveness of agentic use cases.
The user's experience points to a likely shift in how Anthropic is enforcing or calculating Pro plan limits, a change that was not accompanied by public-facing communication at the time of the post. Such shifts are not unprecedented: Anthropic has periodically adjusted rate-limit windows, recalibrated what counts against usage quotas, or tightened enforcement during periods of high platform load or infrastructure changes. The timing — described as beginning "since yesterday" — suggests either a backend policy update or a change in how token consumption from agentic tool-use loops is accounted for, as opposed to straightforward conversational tokens alone.
The broader significance of this complaint lies in the structural tension between Anthropic's tiered pricing model and the emergence of agentic, high-throughput use cases that the Pro plan was not originally designed to accommodate. Claude Code, released as Anthropic's terminal-based agentic coding product, fundamentally changes the consumption profile of a typical Pro subscriber. What once described a power user — someone sending long, detailed prompts and reading lengthy responses — now describes a relatively light user compared to those running autonomous multi-step coding agents. Anthropic's Max plan, priced significantly above Pro, is implicitly positioned as the intended tier for this class of usage, and user frustration over feeling "forced" into an upgrade reflects a product segmentation that may not have been clearly communicated at the time Claude Code became widely adopted.
This dynamic is consistent with a broader industry pattern in which AI providers initially set usage limits calibrated to conversational interaction, then find those limits structurally misaligned with agentic and developer-tooling workloads that emerged afterward. OpenAI faced analogous friction when Codex and later GPT-4-based coding agents became common, and Google has similarly had to recalibrate Gemini API quotas as agentic frameworks proliferated. For Anthropic, the challenge is particularly acute because Claude Code is a first-party product that actively encourages the very usage patterns most likely to strain Pro plan limits, creating a feedback loop where Anthropic's own tooling drives users toward its higher-margin subscription tiers.
Read original article →