Anthropic cuts off the ability to use Claude subscriptions with OpenClaw and third-party AI agents
Are you a subscriber to Anthropic's Claude Pro ($20 monthly) or Max ($100-$200 monthly) plans and use its Claude AI models and products to power third-party AI agents like OpenClaw ? If so, you're in for an unpleasant surprise. Anthropic announced a few hours ago that starting tomorrow, Saturday, April 4, 2026, at 12 pm PT/3 pm ET, it will no longer be possible for those Claude subscribers to use their subscriptions to hook Anthropic's Claude models up to third-party agentic tools, citing the strain such usage was placing on Anthropic's compute and engineering resources, and desire to serve a wide number of users reliably. "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-pa
Are you a subscriber to Anthropic's Claude Pro ($20 monthly) or Max ($100-$200 monthly) plans and use its Claude AI models and products to power third-party AI agents like OpenClaw? If so, you're in for an unpleasant surprise.
Anthropic announced a few hours ago that starting tomorrow, Saturday, April 4, 2026, at 12 pm PT/3 pm ET, it will no longer be possible for those Claude subscribers to use their subscriptions to hook Anthropic's Claude models up to third-party agentic tools, citing the strain such usage was placing on Anthropic's compute and engineering resources, and desire to serve a wide number of users reliably.
"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," wrote Boris Cherny, Head of Claude Code at Anthropic, in a post on X. "Capacity is a resource we manage thoughtfully and we are prioritizing our customers using our products and API."
The company also reportedly sent out an email to this effect to some subscribers. However, it's not certain if subscribers to Claude Team and Enterprise will be impacted similarly. We've reached out to Anthropic for further clarification and will update when we hear back.
To be clear, it will still be possible to use Claude models like Opus, Sonnet, and Haiku to power OpenClaw and similar external agents, but users will now need to opt into a pay-as-you-go "extra usage" billing system or utilize Anthropic's application programming interface (API), which charges for every token of usage rather than allowing for open-ended usage up to certain limits, as the Pro and Max plans have allowed so far.
The reason for the change: 'third party services are not optimized'
The technical reality, according to Anthropic, is that its first-party tools like Claude Code, its AI vibe coding harness, and Claude Cowork, its business app interfacing and control tool, are built to maximize "prompt cache hit rates"—reusing previously processed text to save on compute.
Third-party harnesses like OpenClaw often bypass these efficiencies. “Third party services are not optimized in this way, so it's really hard for us to do sustainably,” Cherny explained further on X.
He even revealed his own hands-on attempts to bridge the gap: “I did put up a few PRs to improve prompt cache hit rate for OpenClaw in particular, which should help for folks using it with Claude via API/overages.”
Prior to the news, Anthropic had also begun imposing stricter Claude session limits every 5 hours of usage during business hours (5am-11am PT/8am-2pm ET), meaning that the number of tokens you could send during those sessions dropped.
This frustrated some power users who suddenly began reaching their limits far faster than they had previously — a change Anthropic said was to help "manage growing demand for Claude" and would only affect up to 7% of users at any given time.
Discounts and credits to soften the blow
Anthropic is not banning third-party tools entirely, but it is moving them to a different ledger. The new "Extra Usage" bundles represent a middle ground between a flat-rate subscription and a full enterprise API account.
- The Credit: To "soften the blow," Anthropic is offering existing subscribers a one-time credit equal to their monthly plan price, redeemable until April 17.
- The Discount: Users who pre-purchase "extra usage" bundles can receive up to a 30% discount, an attempt to retain power users who might otherwise churn.
- Capacity Management: Anthropic’s official statement noted that these tools put an "outsized strain" on systems, forcing a prioritization of "customers using our core products and API."
'The all you-can-eat buffet just closed'
The response from the developer community has been a mixture of analytical acceptance and sharp frustration.
Growth marketer Aakash Gupta observed on X that the "all-you-can-eat buffet just closed," noting that a single OpenClaw agent running for one day could burn $1,000 to $5,000 in API costs. “Anthropic was eating that difference on every user who routed through a third-party harness,” Gupta wrote. “That's the pace of a company watching its margin evaporate in real time.”
However, Peter Steinberger, the creator of OpenClaw who was recently hired by OpenAI, took a more skeptical view of the "capacity" argument.“Funny how timings match up,” Steinberger posted on X. “First they copy some popular features into their closed harness, then they lock out open source.”
Indeed, Anthropic recently added some of the same capabilities that helped OpenClaw catch-on — such as the ability to message agents through external services like Discord and Telegram — to Claude Code.
Steinberger claimed that he and fellow investor Dave Morin attempted to "talk sense" into Anthropic, but were only able to delay the enforcement by a single week.
User @ashen_one, founder of Telaga Charity, voiced a concern likely shared by other small-scale builders: “If I switch both [OpenClaw instances] to an API key or the extra usage you're recommending here, it's going to be far too expensive to make it worth using. I'll probably have to switch over to a different model at this point.”
.“I know it sucks,” Cherny replied. “Fundamentally engineering is about tradeoffs, and one of the things we do to serve a lot of customers is optimize the way subscriptions work to serve as many people as possible with the best mode
Licensing and the OpenAI shadow
The timing of the crackdown is particularly notable given the talent migration. When Steinberger joined OpenAI in February 2026, he brought the "OpenClaw" ethos with him.
OpenAI appears to be positioning itself as a more "harness-friendly" alternative, potentially using this moment as a customer acquisition channel for disgruntled Claude power users.
By restricting subscription limits to their own "closed harness," Anthropic is asserting control over the UI/UX layer. This allows them to collect telemetry and manage rate limits more granularly, but it risks alienating the power-user community that built the "agentic" ecosystem in the first place.
The Bottom Line
Anthropic’s decision is a cold calculation of margins versus growth. As Cherny noted, "Capacity is a resource we manage thoughtfully."
In the 2026 AI landscape, the era of subsidized, unlimited compute for third-party automation is over.
For the average user on Claude.ai, the experience remains unchanged; for the power users running autonomous offices, the bell has tolled.
VentureBeat AI
https://venturebeat.com/technology/anthropic-cuts-off-the-ability-to-use-claude-subscriptions-with-openclaw-andSign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
claudemodelannounce
QUANTUM HORIZONS Your Passwords Have an Expiry Date. Nobody Told You.
By The Architect NEO | April 2026 You know that friend? The one at every barbecue who, somewhere between the third burger and the dying embers, starts talking about encryption? The one who makes you check if your webcam has tape over it? The one who said "don't use that free Wi-Fi" at the airport in 2019 and you thought they were being dramatic? That friend was right about everything. And they're about to be right again — about something much, much bigger. THE QUIET HEIST NOBODY'S REPORTING Right now, while you're reading this on a Tuesday lunchbreak or doomscrolling at 11pm, encrypted data is being stolen. Not decrypted. Not read. Not yet. Stored. Intelligence agencies across the globe have a name for it: "Harvest Now, Decrypt Later." The idea is brutally simple. Steal encrypted data toda

Cloud Cost Anomaly Detection: How to Catch Surprise Bills Before They Hit
Cloud Cost Anomaly Detection: How to Catch Surprise Bills Before They Hit Cloud bills don't spike gradually. They spike overnight. A misconfigured NAT gateway starts routing all inter-AZ traffic inefficiently on a Friday. A data pipeline job enters an infinite retry loop on Saturday. A developer spins up a p3.8xlarge for a test and forgets to terminate it over a long weekend. By the time you find out, you've already burned through budget that wasn't allocated for it. The problem isn't that anomalies happen. The problem is the detection lag: most teams don't discover a cost spike until the invoice arrives 30 days later. With the right alerting in place, you catch the same spike in under 6 hours. This is the practical guide to setting that up. Why Cloud Bills Spike (And Why You Don't Find Ou

Cloud Observability vs Monitoring: What's the Difference and Why It Matters
Cloud Observability vs Monitoring: What's the Difference and Why It Matters Your alerting fires at 2 AM. CPU is at 94%, error rate is at 6.2%, and latency is climbing. You page the on-call engineer. They open the dashboard. They see the numbers going up. What they cannot see is why — because the service throwing errors depends on three upstream services, one of which depends on a database that is waiting on a connection pool that was quietly exhausted by a batch job that ran 11 minutes ago. Monitoring told you something was wrong. Observability would have told you what. This is not a semantic argument. Teams with mature observability resolve incidents 2.8x faster than teams that rely on monitoring alone, according to DORA research. The gap matters in production. Understanding why the gap e
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Products

Cloud Cost Anomaly Detection: How to Catch Surprise Bills Before They Hit
Cloud Cost Anomaly Detection: How to Catch Surprise Bills Before They Hit Cloud bills don't spike gradually. They spike overnight. A misconfigured NAT gateway starts routing all inter-AZ traffic inefficiently on a Friday. A data pipeline job enters an infinite retry loop on Saturday. A developer spins up a p3.8xlarge for a test and forgets to terminate it over a long weekend. By the time you find out, you've already burned through budget that wasn't allocated for it. The problem isn't that anomalies happen. The problem is the detection lag: most teams don't discover a cost spike until the invoice arrives 30 days later. With the right alerting in place, you catch the same spike in under 6 hours. This is the practical guide to setting that up. Why Cloud Bills Spike (And Why You Don't Find Ou

QUANTUM HORIZONS Your Passwords Have an Expiry Date. Nobody Told You.
By The Architect NEO | April 2026 You know that friend? The one at every barbecue who, somewhere between the third burger and the dying embers, starts talking about encryption? The one who makes you check if your webcam has tape over it? The one who said "don't use that free Wi-Fi" at the airport in 2019 and you thought they were being dramatic? That friend was right about everything. And they're about to be right again — about something much, much bigger. THE QUIET HEIST NOBODY'S REPORTING Right now, while you're reading this on a Tuesday lunchbreak or doomscrolling at 11pm, encrypted data is being stolen. Not decrypted. Not read. Not yet. Stored. Intelligence agencies across the globe have a name for it: "Harvest Now, Decrypt Later." The idea is brutally simple. Steal encrypted data toda

Cloud Observability vs Monitoring: What's the Difference and Why It Matters
Cloud Observability vs Monitoring: What's the Difference and Why It Matters Your alerting fires at 2 AM. CPU is at 94%, error rate is at 6.2%, and latency is climbing. You page the on-call engineer. They open the dashboard. They see the numbers going up. What they cannot see is why — because the service throwing errors depends on three upstream services, one of which depends on a database that is waiting on a connection pool that was quietly exhausted by a batch job that ran 11 minutes ago. Monitoring told you something was wrong. Observability would have told you what. This is not a semantic argument. Teams with mature observability resolve incidents 2.8x faster than teams that rely on monitoring alone, according to DORA research. The gap matters in production. Understanding why the gap e

How to Write Custom Semgrep Rules: Complete Tutorial
Why write custom Semgrep rules Semgrep ships with over 2,800 community rules and 20,000+ Pro rules that cover common security vulnerabilities, best practice violations, and correctness issues across more than 30 programming languages. For many teams, these pre-built rule sets are enough to catch the most critical problems. But every codebase has patterns, APIs, and conventions that are unique to its organization - and that is where custom rules become essential. Custom Semgrep rules let you codify institutional knowledge into automated checks. When a senior engineer discovers a subtle misuse of an internal API, they can write a rule that catches that mistake everywhere it appears and prevents it from being introduced again. When your security team identifies a vulnerability pattern specifi


Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!