← X

@Brulee_x Working on fixing this, will feel better tomorrow. We’re going to send

X · bcherny · April 4, 2026
Anthropic community members criticized the company's policy restricting third-party automated tool usage on subscription plans, complaining about pricing structures, usage limits, and difficulties obtaining refunds. Users expressed frustration with subscription limitations and questioned the company's competitive positioning compared to alternatives like OpenAI, with some reporting they were switching to competing models. The feedback indicated widespread dissatisfaction with both the technical constraints and the support experience for subscription-related issues.

Detailed Analysis

A wave of user frustration directed at Anthropic and Boris Cherny (@bcherny), an Anthropic engineer associated with Claude Code, erupted across social media following what appears to be a significant policy change restricting third-party tool access to Claude's subscription plans. The posts, addressed directly to Cherny, reveal widespread discontent over Anthropic's decision to curtail or ban the use of unofficial wrappers and automated tools — most notably a tool referred to as "OpenClaw" — under consumer subscription tiers. Users report being denied credits or refunds they were promised, encountering broken compensation links, and finding themselves locked out of workflows they had built over months using Claude's models through these third-party integrations.

The core grievance centers on a perceived betrayal of trust between Anthropic and its developer-adjacent user base. Several respondents describe having paid for API access in good faith, building agentic systems and automation workflows on top of Claude, only to have the rules shifted beneath them. The restriction appears to distinguish between use through Anthropic's own tools — such as Claude Code itself, the Agent SDK, or the official CLI — and use through user-built or third-party wrappers running on subscription tokens. Users are questioning whether self-built automation tools run locally on a Max plan would be permissible, with community members offering informal legal interpretations based on Anthropic's Terms of Service, underscoring the lack of clear official guidance. Complaints about the $20/month plan's message limits, particularly in the context of agentic workflows that rapidly consume quota, further compound the dissatisfaction.

The backlash also carries a distinctly competitive dimension. Multiple users cite OpenAI's Codex, Google's Gemini models, Qwen, and open-weight models such as MiniMax and Gemma 4 as viable or superior alternatives, with at least one commenter noting that their internal project had formally banned Claude.ai subscriptions in favor of these alternatives. The sentiment that "competing models are already better" and offer greater scalability for agentic systems reflects a broader industry dynamic in which the gap between frontier closed models and open-weight alternatives has narrowed considerably as of early 2026. Anthropic's move to tighten subscription terms — likely motivated by the substantial token costs associated with heavy agentic use — risks accelerating user migration at precisely the moment when the competitive landscape has become most crowded.

The episode illuminates a structural tension increasingly visible across the AI industry: the mismatch between consumer subscription pricing models and the token-intensive demands of agentic, automated workflows. What was designed as a human-in-the-loop chat product is being stretched by power users into a platform for autonomous multi-session agents, background scripts, and continuous integration pipelines. Anthropic's attempt to draw a line between sanctioned and unsanctioned usage reflects a genuine economic pressure — a small percentage of heavy users can consume a disproportionate share of infrastructure capacity, mirroring historical patterns from ISP bandwidth disputes — but the execution, particularly around refund handling and communication, has generated reputational friction. The direct, public nature of the complaints lodged at a named engineer rather than a corporate support channel also reflects a recurring dynamic in AI-adjacent developer communities, where accountability is sought through social visibility when institutional channels fail.

Read original article →