Detailed Analysis
A Reddit user posting to r/Anthropic reports a noticeable and abrupt degradation in session duration when using Claude Opus 4.8 at High and Extra effort settings, claiming that usage limits are being reached in roughly half the time compared to prior sessions of comparable or even greater complexity. The post highlights that longer, more detailed conversations were previously completed without triggering these limits, making the sudden change feel anomalous rather than attributable to normal variation in prompt length or conversational depth. The user also notes encountering multiple "safety limits" — distinct from standard session caps — while engaging in prompts related to hypothetical biology research, raising the question of whether the two phenomena are connected or whether a new, less transparent restriction policy has been quietly implemented.
The timing and nature of the complaint points to a few plausible explanations, none of which Anthropic has publicly confirmed. One possibility is that the compute cost of running Opus 4.8 at high effort levels has increased due to changes in the model's internal reasoning or chain-of-thought processes, which would naturally accelerate token consumption and rate-limit thresholds even for users whose prompting behavior has not changed. Another possibility is that Anthropic has adjusted its rate-limiting or session-accounting logic server-side, perhaps in response to infrastructure demands or fairness policies, without making a formal announcement to users. The dual occurrence of safety-related interruptions and faster session exhaustion could also suggest that flagged content triggers more computationally intensive moderation pathways, effectively penalizing certain prompt types with accelerated token burn.
The user's reference to Anthropic's reported computing infrastructure deal with SpaceX — presumably related to Starlink or Starshield satellite-based compute capacity — introduces a pointed irony. If Anthropic is actively expanding its compute footprint through high-profile partnerships, the simultaneous tightening of user-facing session limits creates a perception gap between the company's stated capacity ambitions and the lived experience of paying subscribers. This kind of dissonance is a recurring friction point in the AI industry, where infrastructure investment cycles and product-level resource allocation operate on different timelines and under different organizational pressures.
More broadly, the complaint reflects a structural tension in frontier AI deployment: as models like Opus 4.8 grow more capable, their per-query compute cost rises substantially, particularly when extended reasoning, high effort modes, or safety-checking layers are involved. Companies like Anthropic face the challenge of offering powerful models at consumer-accessible price points without either absorbing unsustainable losses or quietly throttling access in ways that erode user trust. The biology research context is also notable — it sits in a gray zone where legitimate scientific inquiry and dual-use biosecurity concerns overlap, and automated safety systems are known to be imprecise, potentially triggering restrictions that consume additional compute or hard-stop sessions in ways users cannot easily anticipate or appeal.
The absence of official communication from Anthropic about either the session limit changes or the safety-limit behavior is the thread's most consequential subtext. Whether the changes are intentional policy, a backend adjustment, or an unintended consequence of recent model or infrastructure updates, the lack of transparency leaves users constructing their own theories. This is a known reputational vulnerability for AI labs: when capability-adjacent restrictions tighten without explanation, users tend to attribute the change to either commercial exploitation or hidden censorship, neither of which serves the company's long-term credibility. Clear, proactive communication about resource limit changes — especially at premium service tiers — would likely defuse much of the frustration evident in posts like this one.
Read original article →