Steven Gonsalvez

Software Engineer

← Back to Banter
|

Anthropic Just Killed Third-Party Harnesses and I'm Properly Gutted

The Email Nobody Wanted 📧

Got this at 1:47am. Because of course bad news arrives at 1:47am.

Anthropic email about third-party harness limits

Starting April 4 at 12pm PT, your Claude subscription no longer covers third-party harnesses. OpenClaw, Hermes, and all the other claws and wrappers. You can still use them, but you'll need to turn on "extra usage" which means pay-as-you-go on top of your subscription.

Your subscription still covers Claude Code and Claude Cowork. But anything else that talks to Claude through a third-party harness? That's now metered separately.

I reckon I saw this coming after the OpenCode crackdown back in January. Anthropic blocked third-party OAuth then, and this is the logical next step. First they stopped you piggybacking your subscription through alternative tools. Now they're explicitly making third-party access a separate billing line.

Why This Stings

Look, I get the business logic. Anthropic can't have half the developer ecosystem routing unlimited Claude calls through wrappers that bypass their usage tracking. Every request through a third-party harness is compute they're paying for that isn't landing on their revenue dashboard the way they want it to.

But it kills a pattern that works for a lot of people as a daily driver. Plenty of folk don't run Claude Code at all. They use the intelligence of the model and the convenience of a flat subscription plan to build their own ecosystem around it. Custom harnesses, agent orchestrators, workflow tools that talk to Claude through these third-party wrappers. That's the whole point. Not everyone is an engineer who wants to live in a terminal. Stripping that away is going to push a lot of non-engineering users, the ones who were happily building with tools like OpenClaw and Hermes, into exploring other options entirely.

The Codex Question

I've been running both for months. Claude Code for the familiar workflow, Codex for the parallel instances and that ridiculous context window. This email tips the scales.

If my custom harnesses now cost extra on Claude but Codex lets me run the same workflows through their CLI with my subscription, the maths does itself. I don't want to switch. Claude Code's skill system, the hooks, the agent architecture. I built my entire workflow around it. But I also don't want to pay two bills for what used to be one.

Sad to see this happen. Properly gutted, if I'm honest.

Bottom line: Anthropic is drawing a line around Claude Code and Cowork as the sanctioned ways to use Claude for coding. Everything else is now metered. The walled garden gets taller. Time to properly evaluate whether Codex earns the switch, or whether the extra usage costs are worth staying in the Claude ecosystem. Either way, this week changed the calculus.

Share𝕏in

Comments & Reactions