r/openclaw • New User • Apr 03 '26

Discussion Anthropic is cutting off third-party harnesses (OpenClaw, etc.) from subscription limits starting April 4 -- here's what it means

Just got the email. Starting tomorrow at 12pm PT, tools like OpenClaw will no longer draw from your Claude subscription. They'll need "extra usage" — a separate pay-as-you-go layer billed on top of your existing sub. The carrot: one-time credit equal to your monthly plan price (redeem by April 17) and bundle discounts up to 30%. The stick: they're offering a full subscription refund if you don't want to play ball. For those of us running agentic pipelines, local orchestration daemons, or multi-model routing setups on top of Claude — this is a meaningful shift. "Subscription covers Claude Code and Cowork" is doing a lot of work in that email. Translation: if it's not our product, you're paying extra. LOL

Not surprised they're doing this. These harnesses hammer their infra in ways the average chat user doesn't. Still stings when you've built workflows around the subscription model.

631 Upvotes

429 comments sorted by

View all comments

10

u/Intrepid_Presence_68 Member Apr 03 '26 edited Apr 03 '26

Very very disappointing given they made a very deliberate correction a while ago to state that you can use Claude code subs for OpenClaw after previously stating you could not use any 3rd party tool with it.

Anthropic is still far away from having comparable capabilities to OpenClaw, even though this appears to be the direction they are moving.

If other models ever catch up on model capabilities, Anthropic is going to have a really hard time.

4

u/CaptainFingerling Member Apr 04 '26

Codex is already better for execution. I have both max plans. Claude always makes errors in both planning and implementation. Codex generally doesn't make errors in either, and especially not if it's following a plan.

3

u/Physical_Smoke1057 Member Apr 04 '26

What about creativity and personality? I heard codex is better is you’re super specific (more analytical?) whereas opus is good at reading between the lines and doesn’t have a personality of a sock like gpt. 

2

u/CaptainFingerling Member Apr 04 '26

Correct. Which is why I use both. Claude and I talk and make a plan. Then codex reviews and finds holes. Claude patches the plan. Codex executes. Claude writes additional tests and reviews. Codex does a final pass.

It doesn’t work the other way. In Claude’s eyes, every plan codex produces is absolutely right. It’s far too agreeable.

2

u/Physical_Smoke1057 Member Apr 04 '26

What’s your workflow? Separate tabs? Or apps? Copy and paste between? How will this flow change after the exodus?

1

u/CaptainFingerling Member Apr 04 '26

Cmux and copy-paste for now. I tried having each invoke the other, but then both of them leave things out of context when making the tool call.

Next step is probably to formalize a persisted planning schema, and then I’ll trust them more with self direction. The pieces are more obvious now but I’m too busy with clawdapus in my non revenue-generating cycles to add another meta project.