Anthropic just cut off Claude subscriptions from OpenClaw

By Linas Valiukas · April 4, 2026

Anthropic sent an email this morning. Starting today — April 4, 12pm PT — your Claude subscription no longer covers OpenClaw. Want to keep using it? Turn on "extra usage," a pay-as-you-go layer billed on top of your existing subscription.

This isn't a surprise if you've been following the story. Anthropic quietly blocked subscription OAuth tokens back in January. But that was silent, technical, deniable. This is an email to every subscriber, with a date and a deadline. They're making it official.

What the email says

The email, shared on Hacker News by user firloop, lays it out plainly:

"Starting April 4 at 12pm PT / 8pm BST, you'll no longer be able to use your Claude subscription limits for third-party harnesses including OpenClaw. You can still use them with your Claude account, but they will require extra usage, a pay-as-you-go option billed separately from your subscription."

Your subscription still covers Claude Code and Claude Cowork. Anything else now needs separate billing. They're starting enforcement with OpenClaw today and say more third-party tools will follow.

The sweeteners: a one-time credit equal to your monthly plan price ($20 for Pro, $100 for Max 5x, $200 for Max 20x), redeemable by April 17. Discounts up to 30% on pre-purchased token bundles. And a refund option coming in a follow-up email.

Although some people on Reddit are reporting that the credit redemption doesn't actually work. So there's that.

The justification — and the real reason

Boris Cherny, Anthropic's Head of Claude Code, told VentureBeat: "We've been working hard to meet the increase in demand for Claude, and our subscriptions weren't built for the usage patterns of these third-party tools." He added that "capacity is a resource we manage thoughtfully and we are prioritizing our customers using our products and API."

There's a technical angle that makes Anthropic's case stronger than pure economics. Claude Code is optimized for high prompt cache hit rates — reusing previously processed context to reduce compute. OpenClaw largely bypasses this. GitHub issues document OpenClaw getting roughly 10% cache hit rates versus Claude Code's much higher numbers. Dynamic system prompts, injected metadata, and conversation structures that don't match Anthropic's caching assumptions mean OpenClaw sessions can cost 10-100x more compute per interaction.

A Claude Max subscriber paying $200/month can burn through $1,000-$5,000 in API-equivalent compute when OpenClaw runs around the clock. Anthropic was eating the difference. As one Reddit commenter put it: "All subscription systems rely on charging customers for about 60% of the actual usage. Since 60% of people use less than they pay for, you make a profit off those users... They are going with option three: get rid of the highest usage users."

Peter Steinberger's response

OpenClaw's creator didn't hold back. Steinberger said on X that both he and Dave Morin "tried to talk sense into Anthropic" and the best they managed was delaying the announcement by a week. He characterized the Friday afternoon timing as an attempt to bury the news.

His broader take: "First they copy some popular features into their closed harness, then they lock out open source." He noted that many users had signed up for Claude subscriptions specifically because of OpenClaw. He also gave Boris Cherny credit "for doing what he can to soften the fallout."

Mixed feelings from the guy who created the thing that's being cut off. Fair enough.

The timing and the optics

Less than 24 hours' notice. Announced on a Friday afternoon. Communicated via personal Twitter accounts from employees before some people had even received the email.

One Reddit user in r/openclaw captured the mood: "I continue to be impressed by the professional communication from Anthropic. Between rolling out major changes with less than 24h on Friday afternoon and announcing changes only on employee's personal twitter accounts, it's a class act top to bottom over there." Another was blunter: "They're a college group project masquerading as a business."

The contrast with the January token block is interesting though. Back then — no warning at all. Users woke up to 403 errors and silence for five weeks before Anthropic acknowledged it. This time there's an email, a date, credits, and a refund path. That's progress, even if the timing stinks.

Worth noting what was happening in the background. Anthropic launched Claude Code Channels in late March — messaging Claude via Telegram and Discord. They launched Claude Cowork (Dispatch) on March 17. They've been building their own version of what OpenClaw does. And now they're cutting off the competition's access to their models on favorable terms. The pattern is hard to miss.

The self-preferencing debate

This is where the Hacker News thread gets heated. Claude already has hard token limits — weekly caps, 5-hour usage windows. If those limits exist and you stay within them, why does it matter whether you typed the prompts yourself or OpenClaw sent them?

One HN commenter nailed it: you can max your plan just as easily with Claude Code's own /loop command. The tokens consumed are the same. The difference is which product consumed them.

Anthropic's counterargument — the cache hit rate problem — is technically valid. Claude Code and OpenClaw consuming the same number of tokens doesn't mean they cost Anthropic the same amount of compute. If OpenClaw's cache misses mean 10x the GPU hours, the economics genuinely are different.

But the HN thread also surfaced a February incident where Anthropic had explicitly said you could use subscription tokens with OpenClaw, only to reverse course weeks later. As one Redditor in r/ClaudeCode put it: "Very very disappointing given they made a very deliberate correction a while ago to state that you can use Claude Code subs for OpenClaw after previously stating you could not."

Where people are going

The Reddit threads read like a migration planning session. Most people are heading the same direction: OpenAI.

OpenAI hired Peter Steinberger in February and officially supports OpenClaw via Codex OAuth. GPT-5.4 isn't Opus — multiple Redditors admit it's "not as human" — but it works. One user noted they'd set up OpenClaw with OpenAI weeks ago when they first heard this was coming, and it freed up their Claude subscription for heavy coding work.

Others are going further. OpenRouter with model routing is popular — letting you send different tasks to different models based on complexity. Kimi and Qwen3.6-plus (currently free on OpenRouter) keep coming up. One user in r/openclaw said they'd moved 85% of their workflows to Haiku as default and rerouted heartbeat checks to a free model, dropping their bill from $140/month to $12.

And some people aren't going anywhere. The Opus model is that good. As one commenter admitted: "I actually setup OpenClaw to use OpenAI a few weeks ago when I had first heard they were doing this and I started using Claude a lot more... and now I am actually asking myself, do I really need OpenClaw at all."

Which might be exactly the outcome Anthropic is betting on.

A few people think this is fine, actually

Not everyone is upset. A r/ClaudeCode commenter cheered: "This is Fantastic News. Couldn't be happier. Gets rid of the crap out there that bogs down the system." Another in r/Anthropic said if this means Claude Code limits go back to normal, it's worth it.

There's some logic there. Anthropic's been cutting token limits for Claude Code users over the past month. If OpenClaw sessions genuinely consume disproportionate compute, removing that load could improve service for everyone else. "They've been cutting tokens for their core clients recently because of overload on the systems," one Redditor wrote. "It 100% totally makes sense."

From January to April: the full timeline

The escalation has been steady:

• January 9 — Anthropic silently blocks subscription OAuth tokens server-side. Users wake up to 403 errors. No announcement.
• January 27 — OpenClaw renamed from "Clawdbot" after Anthropic trademark complaints.
• February 11-14 — Google starts banning Antigravity accounts that used OpenClaw. No warning, mid-billing cycle.
• February 14 — Peter Steinberger joins OpenAI.
• February 17 — Anthropic finally publishes updated Consumer Terms of Service making the ban official.
• March 17 — Anthropic launches Claude Cowork (Dispatch), their direct OpenClaw competitor.
• Late March — Anthropic ships Claude Code Channels for Telegram and Discord messaging.
• April 4 — Anthropic formally ends subscription coverage for all third-party harnesses, starting with OpenClaw.

Build the competitor. Cut off the competition. Classic platform move.

What this means for you

If you're running OpenClaw with a Claude subscription, you have a few options as of today:

• Turn on extra usage. Keep your subscription for Claude Code and pay separately for OpenClaw at pay-as-you-go rates. Grab the one-time credit before April 17.
• Switch to OpenAI. GPT-5.4 via Codex OAuth officially supports OpenClaw. Not Opus-quality, but it works and the subscription covers it.
• Route through OpenRouter. Send different tasks to different models based on cost and capability. Some people are running 85% of tasks on cheaper models and only hitting Opus when it matters.
• Go API-only. Drop the subscription, use a standard Anthropic API key, pay per token. You lose the flat-rate safety net but gain full control.
• Cancel entirely. Anthropic said a refund email is coming. If you only subscribed for OpenClaw, this might make sense.

The bigger problem is reliability

This is the third time in four months that self-hosted OpenClaw users have had their setup blown up by a provider policy change. January: Anthropic blocks tokens. February: Google bans accounts. April: Anthropic formally cuts subscription access.

Each time, people scrambled. Migrated providers, reconfigured credentials, rebuilt automations. One Redditor said they'd literally been suspended weeks ago for the same thing Anthropic is now formally announcing. If you've built real workflows — customer responses, inbox triage, appointment scheduling — that scramble means downtime. Messages go unanswered. Tasks don't run.

A managed OpenClaw service deals with this so you don't have to. TryOpenClaw.ai manages API credentials, stays ToS-compliant, and handles provider migrations when policies shift. No surprise Friday emails. No broken credit redemption links. No Saturday morning rebuilds. Starts at $39/month.