TL;DR

Anthropic killed third-party tool access through Claude subscriptions today, April 4, at 12 PM PT. If you’ve been running OpenClaw or similar agents on your Claude Pro or Max subscription, that stops working now. You’ll need to switch to pay-as-you-go “extra usage” billing or use an API key. Anthropic is offering a one-time credit and up to 30% off usage bundles to ease the transition, but for heavy users, costs are going up significantly.

What Happened

Boris Cherny, Head of Claude Code at Anthropic, posted on X that Claude subscriptions would no longer cover usage on third-party tools like OpenClaw, effective April 4, 2026, at 12 PM PT.

His reasoning: “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: “Capacity is a resource we manage thoughtfully and we are prioritizing our customers using our products and API.”

That’s the diplomatic version. Here’s the blunter translation: third-party tools were hammering Anthropic’s infrastructure at subscription rates that didn’t cover the cost.

How OpenClaw Was Using Claude Subscriptions

For anyone unfamiliar, OpenClaw is an open-source AI agent with over 247,000 GitHub stars. It lets you run autonomous tasks (shell commands, browser control, file management, calendar, email) all triggered through messaging platforms like Signal, Telegram, or Discord.

The trick that made it so popular with Claude users: OpenClaw could plug into a Claude Pro or Max subscription by grabbing the consumer OAuth token and sending the same headers as the official Claude Code client. It was spoofing Claude Code’s client identity, piggybacking on subscription rates designed for individual use through Anthropic’s own interface.

It worked. Thousands of developers ran OpenClaw agents powered by Claude models at their flat subscription rate — $20/month for Pro, $100/month for Max, regardless of how much compute they actualy consumed.

Cherny acknowledged the gap: “Third-party services are not optimized in this way, so it’s really hard for us to do sustainably.”

What Your Options Are Now

If you were using Claude through OpenClaw or any other third-party harness, you have two paths:

Option 1: Extra usage billing. Enable pay-as-you-go “extra usage” on your existing Claude subscription. Usage from third-party tools gets billed separately from your subscription, at metered rates.

Option 2: API key. Authenticate your third-party tool with a standard Claude API key and pay standard API pricing.

Anthropic is sweetening the transition with two offers:

  • A one-time credit equal to your monthly subscription cost, redeemable by April 17
  • Up to 30% off when pre-purchasing bundles of extra usage

For light users, the credit might cover a month of adjustment. For power users running multiple OpenClaw instances, the math changes fast.

The Cost Reality

One developer on X did the math publicly. They were running two OpenClaw instances on a Max subscription and estimated that switching both to API billing would cost several times what they were paying. Their response: “It’s going to be far too expensive to make it worth using.”

That’s the core tension. The subscription model gave people a flat rate to run heavy agentic workloads. API pricing scales with usage. For anyone who was relying on that flat rate to make their workflow affordable, this isn’t just a billing change. It’s a workflow disruption.

The Steinberger Factor

There’s a competitive angle here that’s hard to ignore.

Peter Steinberger, the Austrian developer who created OpenClaw (originally named Clawdbot, then briefly Moltbot after Anthropic sent trademark complaints), announced in February 2026 that he was joining OpenAI. The project moved to an open-source foundation.

Anthropic’s decision to wall off Claude from OpenClaw came just weeks after Steinberger’s defection. The timing is hard to dismiss. Anthropic has no reason to keep subsidizing infrastructure for a tool whose creator now works at their biggest competitor.

The business logic is obvious, but developers who built around this access pattern feel like collateral damage in a corporate spat they didn’t sign up for.

The name changes alone tell the story of this relationship souring. Steinberger originally called the project Clawdbot — a clear nod to Claude. Anthropic sent trademark complaints. He renamed it to Moltbot. Three days later, he changed it again to OpenClaw because “Moltbot never quite rolled off the tongue.” Then he left for OpenAI. And now Anthropic is cutting off the infrastructure his tool relied on. It’s a clean breakup arc.

The Bigger Pattern

AI companies across the board are tightening control over how their models get consumed, and this move fits the pattern.

When Claude Pro launched, third-party integrations were a feature, not a bug. They drove adoption. They got Claude into developer workflows through tools people already used. But as demand scaled and agentic workloads started consuming disproportionate compute, the economics stopped working.

Anthropic isn’t the first to face this. OpenAI has gone through multiple rounds of rate limit tightening. Google’s Gemini API has usage caps that make heavy agentic use expensive at scale. The pattern repeats: open access attracts users, heavy usage breaks the unit economics, and companies pull back.

There’s also the broader context of what happened just days ago. On April 1, Anthropic’s entire Claude Code source (512,000 lines of TypeScript) leaked through an npm package. That leak exposed exactly how first-party tools authenticate with Claude’s backend, which likely made it even more urgent to lock down third-party access that was mimicking those same authentication patterns.

The question now is whether pushing everyone to API billing helps or hurts Claude’s third-party adoption long-term. Developers who built workflows around the subscription model have to decide if metered pricing still makes sense, or if cheaper models from DeepSeek, Meta’s Llama 4, or OpenAI are worth the switch.

What This Means for OpenClaw Users

If you’re an OpenClaw user running on Claude, here’s what to do right now:

  1. Check your setup before 3 PM ET today. That’s when the cutoff happens, and your existing sessions may break.
  2. Grab the one-time credit before it expires April 17. Go to your Anthropic billing dashboard and claim it.
  3. Run openclaw stats or check your recent activity to figure out how many tokens you’re actually burning per day. Compare that against API pricing.
  4. OpenClaw supports multiple providers. If Claude’s API pricing doesn’t work for your usage patterns, DeepSeek and GPT models are also options.
  5. Look at the extra usage bundles. The 30% discount on pre-purchased bundles might make the math work if your usage is predictable.

FAQ

Can I still use Claude with OpenClaw?

Yes, but not through your subscription. You’ll need to either enable extra usage billing on your account or use a Claude API key. Both are metered by usage.

How much will it cost compared to my subscription?

It depends entirely on your usage volume. Light users (a few agent tasks per day) might see costs similar to their subscription. Heavy users running multiple persistent agents could pay several times more.

Does this affect Claude Code?

Nope. Claude Code is Anthropic’s own tool and keeps working on your Pro or Max subscription like before. They’re only cutting off third-party harnesses.

Is Anthropic blocking OpenClaw specifically?

The policy applies to all third-party tools, not just OpenClaw. But OpenClaw was by far the largest source of third-party subscription usage, so it’s the primary tool affected in practice.

Will the one-time credit cover my transition?

The credit equals one month of your current subscription ($20 for Pro, $100 for Max). Whether that covers a month of API usage depends on how heavily you use third-party tools.

My Take

Running agentic workloads at flat subscription rates was never going to scale. Everyone kind of knew that. The spoofed client headers were a hack, and the free ride had an expiration date everyone could see.

But the execution stings. Developers built real workflows around this access pattern. Some built businesses on it. Giving them two weeks of credits and a “good luck with API pricing” feels rushed — especially since the Steinberger-joins-OpenAI timeline makes the whole thing look more retaliatory than strategic.

The 30% bundle discount is a decent olive branch. If Anthropic follows up with tiered agentic pricing — something between flat subscriptions and raw API rates — they could keep most of these users. If they don’t, a lot of OpenClaw power users are going to migrate to cheaper models, and Anthropic loses the developer loyalty that third-party tools were building for them.

For now, claim your credits, do the math, and decide if Claude is still worth it for your agentic workflows. The model quality hasn’t changed. Just the price of access.