Anthropic promised 20x more usage. Then developers hit a weekly ceiling.

The Lawsuit

Anthropic sells its top-tier Claude Max subscription with the promise of 20 times more usage than its $20-a-month Pro plan. But developers paying $200 a month can still hit a separate weekly ceiling - and an expanded class-action lawsuit filed Tuesday argues Anthropic didn't make that clear enough.

The dispute over Anthropic's $100 Max 5x and $200 Max 20x tiers points to a bigger problem within the AI sector: Companies are trying to package unpredictable amounts of compute into straightforward monthly subscriptions. Those plans get harder to understand when the advertised usage comes with additional restrictions. If the plaintiffs succeed, the case could set a precedent for how clearly AI providers have to explain those restrictions before developers sign up.

The Anatomy of "20x"

Anthropic's documentation states that its Max 5x and 20x multipliers apply "per session," with usage limits resetting every five hours. But the five-hour window isn't the only limit since Anthropic also imposes a weekly usage cap across all models and says it may add other restrictions to manage capacity.

That's pertinent for Claude Code users whose interactive coding sessions count toward the same plan limits. Once that included usage runs out, developers either have to wait for it to reset or pay more to keep working, which is where the usage promise gets murky. It tells you how Max compares with Pro, not how much actual coding a developer can expect for $200 a month.

According to the complaint, which The Verge first reported, Anthropic introduced weekly limits in late July 2025 - months after Max launched in April - while continuing to market the plans with its 5x and 20x usage claims. The plaintiffs allege those constraints weren't adequately disclosed during subscription.

Anthropic has pushed back on that characterization, arguing in its motion to dismiss an earlier version of the case that customers could access information about the limits through hyperlinks during purchase. The company compared those disclosures to the information on a product label, which customers can find by turning over the package before deciding whether to buy it.

Fixed-Price Compute's Dilemma

And yet, Claude Max isn't the only subscription where it's difficult to know exactly how much work you're getting for the monthly price. That's partially because coding tasks can vary so much. While a quick fix might not make much of a difference to a developer's allowance, a more complicated job can burn through it much faster. A usage multiplier doesn't tell developers much about that difference.

How Competitors Price Uncertainty

OpenAI has to account for the same variability with Codex. Its documentation tells subscribers that usage depends on the task, the model, and where the work is being run. Codex can also draw from a shared allowance with other agentic products. Once that allowance runs out, users can buy more credits.

OpenAI has also made Codex more autonomous, allowing it to keep working while it waits for a developer to respond. And the model a developer chooses makes a difference, too: Astra costs 2.5x more per token than GPT-5.6, so that the same allowance can go a lot further with one model than another.

The mechanics aren't identical to Claude Max, and the lawsuit does not accuse OpenAI or other providers of wrongdoing, but both systems show why comparing AI coding subscriptions isn't as simple as looking at their monthly prices. Saying a plan offers substantially more usage still doesn't tell a team how much work it can actually get done before hitting a limit.

Some AI companies are already experimenting with different ways to charge for that work. OpenAI has been testing outcome-based pricing with some enterprise customers, charging only when an agent completes a task rather than metering raw compute. That approach introduces its own problems since someone has to define "success," and failed agent runs become the provider's expense. But it does show that AI companies are recognizing that token- and multiplier-based pricing doesn't always tell developers what's in a subscription.

A Warning Shot for Subscription

If the plaintiffs succeed, other AI providers may have to rethink how they describe their subscriptions. More detail at signup would help, particularly around when usage resets and what restrictions apply. But even that doesn't answer what developers really want to know: How much work can I get done for the price I'm paying?

As coding agents take on larger jobs and work on their own for longer stretches, the Anthropic case could help establish how much providers need to disclose when selling subscriptions whose actual value can vary so much from one workload to the next.

The New Stack reached out to Anthropic for comment on the lawsuit and its Claude Max usage policies and has not received a response. We will update this story if we hear back.