Anthropic's Method to Losing Goodwill in a Few Easy Steps

Comments

Recently, I had the rare opportunity to test several agent harnesses, LLMs, and AI gateways in my daily tasks and greenfield projects. Each discovery befuddled me on the popular sentiment for agentic development. I learned that in the past two weeks, Anthropic has diminished in value for coding with their enshittification, vendor lock in, consumer malpractice, and price gouging, all while open source models are more competitive than ever.

API Reliability

Claude’s API is notoriously unstable, yet it’s the only API provider that is compatible with a Claude subscription. Other API providers like Vertex AI, AWS Bedrock, and Azure only serve the pricier Anthropic API credits. If you want to subscribe to Claude, you’re stuck with Anthropic’s servers. If you’re debugging an incident at work and are using Claude to help, pray that it stays up because you’re only productive when Claude is online.

Claude Code

Claude Code is Anthropic’s primary consumer-facing engineering interface, and once you’re in, you’re locked in. Your Claude subscription-which is a cheaper version of the Anthropic API-is restricted to use with the Claude Code CLI/Desktop, Claude CoWork, or @Claude in Slack. But that isn’t a bad thing! In fact, Claude Code is the most popular and the best agent harness. It’s backed by a large company at the forefront of agentic software development.

As of writing, Claude Code CLI only has around 9100 open Github issues, with small unresolved issues like it completely freezing for the last 6+ months or a screen flickering issue open for more than a year. Each changelog entry has a bug fix in almost every release, which is a sign of reliable and stable software! For those who don’t get it, Anthropic is using Claude Code to write itself, and it shows in its quality. Because they restrict you to their ecosystem, it justifies falling behind better coding harnesses.

For reference, here is what the Claude Code CLI looks like:

And here is what the OpenCode CLI looks like:

I would take OpenCode’s interface any day over Anthropic’s, but I am prohibited from applying my Claude subscription to OpenCode.

Extra Usage

There are FOSS projects to circumvent Anthropic’s policies, which allow you to use your Claude subscription instead of an expensive Anthropic API Key. A notable example is the Pi Coding Agent, which comes with built-in support for Claude OAuth. However, you’ll notice this message at the bottom when you attempt to authenticate with your Claude account:

Warning: Anthropic subscription auth is active. Third-party harness usage draws from extra usage and is billed per token, not your Claude plan limits. Manage extra usage at https://claude.ai/settings/usage.

“Extra usage” is Anthropic’s answer to their plan limits. When you exceed your five hour session or weekly limit, you’re billed through the Anthropic API. This requires consent by the user on their plan and is good for those with long-running AI sessions. When I authenticate with Claude in Pi Coding Agent, it bills from Extra Usage, meaning my subscription doesn’t save me any money.

Fine. It’s a completely different thing when I’m using the tool they force me to use, and they still retract extra usage before I reach my rate limit. Here is a confusing announcement from Claude’s Twitter account on May 13th, 2026:

For the confused, here is the no bullshit summary from Zed’s blog:

Starting June 15, Anthropic is splitting Claude subscription billing into two pools: one for using Claude through Anthropic's first-party tools (such as chat, or the official Claude Code CLI), and another for third-party agent and SDK usage (anything running through ACP, claude -p, or other third-party tools). If you use Claude Code through ACP (in Zed or anywhere else), that usage will no longer draw from your Claude Pro or Max subscription limits. Instead, it draws from a new monthly "Agent SDK credit" that Anthropic is adding to each plan: $20 for Pro, $100 for Max 5x, $200 for Max 20x. Once the credit runs out, continued usage bills at standard API rates if you have extra usage enabled. If you don't, requests stop until your credit resets next billing cycle.

What this means in practice: For anyone using agents heavily, this is a major cost increase. Claude subscriptions previously subsidized agent usage at roughly 15-30x compared to API pricing, and the new credits are billed at full API rates.

Side note: claude -p is a first party tool offered with the claude cli. If I wanted to use the Claude Code CLI and invoke it in my automations, I have to pay more outside of my subscription. So the extra usage ISN’T extra at all! Users didn’t discover this by having their claude -p invocations stop working, but by looking at their billing page and seeing the charges!

Recommended viewing: Louis Rossman has made a few videos on Anthropic’s predatory pricing changes.

This isn’t the first time Anthropic has decimated their goodwill. They also charged extra usage when they “thought” you might be using a third-party tool, even if you weren’t. They did this by detecting if a file with a certain name was present in your session directory. Anthropic then restricted their API contracts, and proxy tools that aim to restore compatibility for Claude subscriptions with third-party harnesses started charging extra usage overnight, with no change to their own query mechanisms.

Dario needs capital, not because inference is expensive, but because model training is. Once you stop training models, you lose the race to AGI. All this self-flagellation wasn’t even for the product, it was for training the next one! That’s like if majority of your college tuition went to the head coach of the football team (which it usually does). To put it bluntly, they have us by the balls.

Vibe Coding

But why do they have us by the balls? Dario and Boris have us convinced that “coding is solved” with their loops. But microwaves didn’t solve cooking. The flood of AI hype through LinkedIn-preaching from executives with lots of money and power to “automate away” engineers through vibecoding software-perpetuates the attitude that code and developers are dispensable and unimportant. It makes us focus on quantity-of what I would generously call “prototypes”-over quality. These leaders need advanced models so they can vibecode with less friction, and Anthropic serves those models for a “cheap” $200 USD per month. (This subsidized price will increase once profitability becomes a priority again.) So Claude is good for those who can’t or don’t code, and the more vibecoders, the more market share Anthropic gets, and the more people they have by the balls.

I leaned into vibecoding during the brief “tokenmaxxing” era, but when Claude went down, I went down. My “agent-driven development” led to skill degradation and a drift in understanding of my own code. To regain my sanity, I returned to what AI coding used to be with Github Copilot: autocomplete. That’s all an LLM is after you strip away the tool calls, subagents, MCP servers, etc. I understand most of what I want to do, and for any gaps, I ask AI to “autocomplete” my understanding/plan/code. That way, the AI can think/plan/code like me, making it easy to review changes. My workflow is now agent-assisted development, not agent-driven.

But are the alternatives besides GPT or Gemini?

Open Source Models

To be clear, I’m not anti-AI. I’m only against unethical companies with anti-consumer practices, and the perpetrators behind them. If you want to autocomplete, like I do, you don’t need Fable, or even Opus; Sonnet works fine. But if you want to use FOSS trusted tools like Zed, OpenCode, Pi, Nanocoder, etc. unchained by a degrading and restrictive ecosystem, you’re looking for other models.

Ever since Ollama, open source models have ranked far below proprietary models released by Google, OpenAI, and Anthropic. This is due to them having less corporate backing and training parameters. Only recently have we seen competition from foreign models like Deepseek, GLM, Kimi, Qwen, Minimax, Xiaomi, Stepfun, etc.

Coding comparison of Sonnet 5, GLM 5.2, and Qwen 3.7 Max on OpenRouter

I’ve used Qwen and GLM and both replaced Sonnet in my OpenCode workflow. With an AI Gateway like OpenRouter, Requesty, Portkey, or Vercel, I can choose any open source model, and it will route my request to the cheapest and most available backend API provider. I can also tweak the providers to optimize for zero data retention, omit sensitive data leaks from my prompts, and restrict more expensive models.

Cost comparison of GLM 5.2, Qwen 3.7 Max, and Sonnet 5 on OpenRouter

Some models are great for research, but horrible for documentation. Other models are great for coding, but horrible for research. With the right harness, subagents, and models (chosen with experimentation), a developer has the tools they need to develop high quality software and not break the bank.¹

In my head, this is what we should be striving for: open, configurable, and repairable systems. We shouldn’t be using security as an excuse for restricting our models and ignoring customer protections.

Conclusion

In my opinion (which may be in the minority), it’s unethical to:

• lock in your customers to a closed system for maximum market gain
• put down the competition when they pose a risk to your product
• make hypocritical claims on how your product increases quality when your own software sucks
• artificially restrict one’s own product as a fear-mongering marketing stunt
• test dynamic pricing on your users to see how much more they’ll pay for less
• change the terms of your product after the sale without notifying your user base

And this is just one of the three giant AI labs. I could write another piece on OpenAI. Anthropic is trying to match the cutthroat and anti-consumer practices of big-tech because the line must go up. Like I did for big-tech, I’ll be taking my business elsewhere, and I encourage you to do the same.

• Today, I use Qwen and GLM for orchestration, Deepseek for searching, and Minimax for file editing.¹

¹ Editor’s note: Original footnote preserved as-is.