Jonathon's AI Wiki

Kahn v. Anthropic — Class Action Over Claude Max Usage Limits

8 min read

Source: raw/reddit-1u78tig.md · ai-research/decrypt-anthropic-usage-limits-lawsuit-2026-06-16.md · ai-research/kahn-v-anthropic-complaint-excerpt-2026-06-16.md URL: https://decrypt.co/371201/anthropic-lawsuit-allegedly-misleading-claude-ai-pricing Date: 2026-06-16

A proposed class action, Kahn v. Anthropic PBC, was filed June 14, 2026 in the U.S. District Court for the Northern District of California (CourtListener docket 73482575), alleging Anthropic oversold the usage on its premium Claude Max plans. Plaintiff Karl Kahn, a Washington DC resident, claims the Max 5x and Max 20x tiers deliver far less than the advertised 5x and 20x of the Pro plan — and that Anthropic never disclosed how usage is actually measured, so subscribers can’t tell what they’re getting. The suit was first reported by The Wall Street Journal; Anthropic declined to comment.

Key Takeaways

  • The core allegation (quoting the complaint). Max 20x (100/mo, marketed as 5x Pro) allegedly delivers “just three-and-a-half times the usage of Pro” (¶7). The complaint also alleges the “50% savings” pitch on Max 20x is false (¶8). (Pro is 200/yr — ~$17/mo billed annually.)
  • Opacity is central. The complaint calls Anthropic’s website “a black box, without any meaningful description of how usage is calculated,” says “session” is never defined, and argues consumers had no way to verify what they received — which counsel Kati Daffan (Vaca Daffan LLP) says is why no similar suit was filed earlier.
  • Evidence cited. Anthropic allegedly emailed Max subscribers in July 2025 spelling out per-model weekly usage per tier, which the suit says fell below the advertised amount. Kahn’s example: after upgrading to Max 20x for Claude Code work, a single five-hour session burned ~15% of his weekly allowance.
  • The claims. Four causes of action — California Consumers Legal Remedies Act (§1750), False Advertising Law (§17500), Negligent Misrepresentation, and Breach of Contract. Amount in controversy exceeds $5 million.
  • The class. All U.S. residents who purchased or upgraded to Max 5x or Max 20x via Claude.com or the Claude desktop app between April 9, 2025 and the present. Relief sought: damages, restitution, injunctive and declaratory relief, attorneys’ fees, and class certification.
  • Context. The filing landed days after the Fable 5 / Mythos 5 launch, which itself drew complaints that the new models consume subscription allowances faster than earlier Claude models — sharpening the long-running tension between flat subscription pricing and per-token inference cost.
  • Status. Allegations are unproven; no ruling has been made, and Anthropic has not responded to the substance publicly.

Field note: the weekly window is account-attached, not subscription-attached (2026-08-05 addition)

[Reddit signal — r/ClaudeAI 2026-08-04, score 43/36 comments — community report, unverified] Source: raw/reddit-1vg47iu.md.

A user PSA describing a billing-mechanics trap that is orthogonal to the litigation above but bears on the same “what exactly did I buy?” question:

  • The 5-hour session limit and the weekly limit are two separate things.
  • The weekly limit runs on a window attached to the account, and it keeps ticking regardless of subscription state. Cancelling does not pause it. Resubscribing does not restart it.
  • Failure mode: burn through the weekly allowance, let the subscription lapse, resubscribe — you come back still at 100% used, with the same countdown still running. Every day between resubscribing and the reset is paid for and unusable.
  • The poster’s advice: check your reset time before you re-subscribe.

A separate same-day thread (r/Anthropic 1vfvfrs, score 49) reports the reset timer displaying as 6 hours 45 minutes rather than the expected 5, which — if accurate — would mean the session window is longer than users assume. Not staged as a source (image-only post) and not verified.

Both are unverified user reports about billing mechanics that Anthropic could change at any time. They are recorded here because the account-attached window claim, if correct, is a non-obvious consequence of how the limits are implemented and is the kind of term-of-service detail the suit above turns on. Verify against current Anthropic billing documentation before acting on it.

Field note: a reported third limit tier that bills before the published ones are exhausted (2026-08-07 addition)

[Reddit signal — r/ClaudeAI 2026-08-07, score 54/53 comments — community report, unverified] Source: raw/reddit-1vhphmc.md.

The most consequential of the community limit reports so far, because it describes a limit that is not the 5-hour window or the weekly window and has no visible meter at all.

The user reports having checked their usage, knowing allowance remained, running a research-mode task on Sonnet, and then being notified mid-task that they had started consuming usage credits — i.e. paying beyond the subscription — while both published limits still showed as not fully depleted. They stopped the task immediately.

The load-bearing part is a verbatim reply from Anthropic’s Fin support agent, quoted in the post:

“Research mode and certain intensive prompts can consume tokens quickly. When you’re doing heavy work within a session, you might hit a usage threshold that triggers credit billing before your 5-hour session or weekly limit shows as fully depleted.”

If accurate, that describes a third, undocumented threshold for “intensive tasks” that can start billing credits independently of the two published windows. The poster’s three specific complaints:

  1. No usage bar to manage against, and no “your limits have been reached — continue at API pricing?” confirmation step.
  2. Billing begins before the subscription allowance is exhausted, which inverts what a subscription is understood to buy.
  3. It is not clearly documented anywhere the poster could find, and is hard to search for.

They are explicit that the amount (~$5) is not the point — the objection is to charging without a visible meter or a consent step.

How to read it. This is a single user report plus a support-bot reply, and support bots are not authoritative on billing architecture; the quote may be a plausible-sounding generalization rather than a description of a real distinct mechanism. But it is more concrete than the usual limit complaint — it names a trigger (research mode / intensive prompts), a behavior (credit billing before depletion), and a first-party source for the explanation. It also sits directly on the allegation the litigation above turns on: that usage measurement is opaque to the person paying for it.

Adjacent same-day signal, not staged (score 10, below the staging bar): a Pro user reporting a drastic drop in per-session capacity and widening gaps between sessions over five days on simple non-coding prompts (reddit-1vhbckf). Directionally consistent, individually worthless as evidence.

The 50% relief was extended, and the complaints did not stop (2026-08-19 addition)

Two things happened at once, and the tension between them is the point.

Anthropic extended the 50% Claude Code weekly limit increase through August 31, 2026. Announced across the subreddits and posted with an Announcement flair in r/Anthropic (raw/reddit-1vrzq72.md, 172 pts); it was the highest-scoring item of the sweep in r/ClaudeAI (raw/reddit-1vrzmx9.md, 1,738 pts) and r/ClaudeCode (raw/reddit-1vrzm9h.md, 758 pts). Whatever else is true, the community reads limit relief as the most consequential news Anthropic ships.

Simultaneously, users reported limits depleting faster than before. raw/reddit-1vsp2e5.md (24 pts / 30 comments) reports session limits hitting “EXTREMELY QUICK” over two days from a user who says they rarely hit them despite heavy use — and, notably, while the usage tab displayed “Your limits are temporarily boosted.” That is the exact inversion of the announced benefit, observed by a user who could see the boost indicator. Lower-scoring reports in the same window say the same thing (raw/reddit-1vssbrr.md, 9 pts: a five-hour limit consumed in twenty minutes; raw/reddit-1vs0s1q.md, 56 pts).

How much weight this carries: less than the earlier field notes in this article. These are low-engagement reports without instrumentation, in a subreddit where limit complaints are constant, and heavier Opus 5 usage is an obvious confound. What makes them worth recording is not the volume but the specific contradiction with a visible UI state — a user watching a “boosted” indicator while burning a window faster than baseline is a cheaply falsifiable claim, and it is the same class of opacity the Kahn complaint alleges: users cannot tell what they are getting.

A product change lands in the middle of this. Claude Code v2.1.234 (2026-08-17) added automatic session continuation when a claude.ai usage limit resets — off-switch in /config → “Continue automatically at usage limit” (see What’s New — Week 34). It changes the experience of hitting a limit from a hard stop to a pause, without changing the allowance. Two honest readings, and the sources support neither over the other: it removes the most painful symptom, and it removes the moment where a user would otherwise notice how fast they are consuming their window.

Graph View

Backlinks