Why did Anthropic cut OpenClaw support?

Anthropic has stopped supporting OpenClaw through Claude subscriptions, citing strain on its systems. The change targets a way some customers use Claude subscription access to deploy AI agents built with OpenClaw. Anthropic said that this kind of usage is creating an "outsized" burden on its infrastructure, prompting the company to restrict access.

The practical effect is that subscribers who were previously able to use Claude in combination with OpenClaw will face new limits. The policy starts on April 4 (with the timing specified as 3PM ET), and users will be unable to use the previous approach unless they pay an added fee or move to an alternative permitted arrangement.

The move matters because it signals how rapidly commercial AI platforms are tightening controls around agent deployment -- especially when agent frameworks can create large, unpredictable compute loads. Even when the requests come from paying customers, platform operators may throttle or reprice workflows that increase demand beyond what they originally planned for.

For U.S. implications, companies and developers that rely on agent tools for productivity, automation, or customer-service work may need to adjust budgets and architectures. If other model providers respond similarly, it could raise the cost of using third-party agent frameworks and reduce the portability of AI agent stacks.

For businesses, this also highlights a key operational issue: "subscription" access may not guarantee unrestricted usage of tooling. Platform terms can change quickly based on capacity, safety, or performance constraints.

If you're building an AI agent stack, the takeaway is to validate whether third-party agent tools remain compatible with your chosen model provider and to plan for possible cost or access changes.