Anthropic backed down: the official OpenClaw CLI workaround (and why it still won't save you)

By Linas Valiukas · April 26, 2026

Three weeks ago Anthropic killed OpenClaw's subscription access with an email and a Friday afternoon deadline. We covered it then. Most of us moved our heaviest workloads to OpenRouter, DeepSeek, or some glued-together combination of both. And then, this Saturday, OpenClaw 2026.4.24 shipped with one quiet line in the release notes that nobody on the corporate comms side seems to have signed off on.

"The bundled Anthropic claude-cli backend is supported again. Anthropic staff told us OpenClaw-style Claude CLI usage is allowed again, so OpenClaw treats claude -p usage as sanctioned for this integration unless Anthropic publishes a new policy."

That's it. No press release, no Boris Cherny tweet thread, no follow-up email to the people who paid for credit packs. Just a release note and a PR link. So: it's back, sort of. Here's the actual workaround, the JSON config that gets you running on your Pro sub again, and the math on why most of us are leaving the model-routing setup we built during the ban exactly where it is.

What actually changed in 2026.4.24

Two things, and they're worth keeping straight because they sound similar.

First: the OAuth-based "subscription token extraction" path is still blocked. That's the one Anthropic shut off in January, doubled down on in April, and clearly never wants back. If your old OpenClaw setup pulled a subscription OAuth token out of the Claude desktop app and pasted it into a config field, that path is dead. Stays dead. People are still getting account bans for it.

Second: shelling out to the locally installed claude CLI - the binary you get from npm install -g @anthropic-ai/claude-cli and authenticate against your Pro/Max account - is now sanctioned. OpenClaw drives it through claude -p in non-interactive mode. From Anthropic's side, that's indistinguishable from a developer scripting Claude Code at the command line, which has always been allowed.

The reasoning, per Boris Cherny on X (the threads are still up if you want to read them): they kill malicious OAuth extraction because it bypasses rate limits and accounting. Native CLI usage flows through Anthropic's normal session quotas, so the high-burn users self-throttle. They don't have to fight you. The session ceiling does it for them.

The exact config

The OpenClaw team posted a step-by-step in issue #63316. Short version:

1. Install the Claude CLI globally. On the same host that runs OpenClaw.

   npm install -g @anthropic-ai/claude-cli
   claude login

   Use the same Anthropic account your Pro or Max subscription is on.
2. Open your OpenClaw config. If you're on the new TOML-based setup that's ~/.openclaw/openclaw.toml. JSON users want ~/.openclaw/openclaw.json. Find the Anthropic provider block.
3. Switch the backend to claude-cli. The block looks like this on TOML:

   [providers.anthropic]
   backend = "claude-cli"
   auth = "cli"
   default_model = "claude-sonnet-4-6"
   binary_path = "claude"

   And this on JSON:

   {
     "providers": {
       "anthropic": {
         "backend": "claude-cli",
         "auth": "cli",
         "default_model": "claude-sonnet-4-6",
         "binary_path": "claude"
       }
     }
   }

4. Clear the API key. If you've got an ANTHROPIC_API_KEY still set in your env, OpenClaw will prefer it over the CLI shell. Remove it from .env, your Docker compose env block, and any systemd unit overrides.
5. Restart the gateway.

   openclaw gateway restart

   Then send one message and check /usage. If the response shows session-quota consumption instead of API spend, you're routed through the CLI.

The Docker users among you have a sharper edge to walk: the official OpenClaw image still doesn't bundle the Claude CLI. Bake it into your own image, or - if you've already tried - stop letting your agent recursive-fix the install. One Reddit user burned $50 in API tokens letting OpenClaw debug its own missing CLI inside the container. Drop the container, spin up a raw Debian VPS, install the CLI globally, run OpenClaw under tmux. Vastly more stable for now.

The catch: 25 messages

Here's the part the release notes don't tell you. The CLI shell respects your subscription's session quota, which is fine for chat. For OpenClaw, it's a problem.

A user in the r/openclaw confirmation thread tested it on a Pro subscription with Sonnet 4.6 as the default. Results: roughly 25 messages per session window, because each OpenClaw round-trip burned about 4% of the quota. Multi-turn agent runs - the kind where your agent thinks, calls a tool, reads the result, thinks again - eat several percent per user message. A single email triage prompt that ends up touching IMAP, search, and a draft can burn 8-12% on its own.

Max 5x and Max 20x stretch this proportionally. Max 20x users in the same thread reported being able to do roughly a workday of agent operation before throttling. Pro users running anything beyond a few back-and-forths a day will hit the ceiling.

For comparison, the burn rate with the old OAuth subscription extraction was effectively unlimited. That's the gap Anthropic closed. The reversal puts you back on subscription billing but with the same throttle every other Claude user has been working under since launch.

What this means for the people who already migrated

If you spent the last three weeks rebuilding around the cheap-and-free model setup, the question is whether to revert. The answer most r/openclaw threads are landing on: don't.

The shape of the new "default" setup that's emerging:

• Claude via the CLI shell as your primary, for interactive chat and high-quality reasoning. Capped naturally by the session quota.
• DeepSeek V4 Flash or GLM-5.1 as your secondary, auto-routed for background jobs - cron, heartbeats, dreaming, anything that can't be allowed to consume your interactive quota.
• An OpenRouter key as fallback, for when both above are throttled or unhappy.

OpenClaw 2026.4.24 actually made V4 Flash the new onboarding default, which suggests the team agrees with this shape even after the Anthropic walkback. The bundled DeepSeek catalog and lighter provider startup in this release exist precisely because nobody serious is treating Anthropic's policy as load-bearing anymore.

The relevant config snippet for the routed setup, in TOML:

[router]
default = "anthropic"
on_quota_exceeded = "deepseek"

[router.jobs]
heartbeat = "deepseek"
cron = "deepseek"
dreaming = "deepseek"
chat = "anthropic"
agent_consult = "anthropic"

That's the version that runs your interactive sessions on your subscription, keeps background work off the quota, and survives the next time Anthropic changes its mind.

The strategic read

This was a quiet climbdown. Three weeks ago Anthropic was telling reporters that OpenClaw bypassed prompt caching, abused subscription pricing, and represented usage patterns "subscriptions weren't built for." Today the same company is telling the OpenClaw team that claude -p reuse is fine. Both can be true at the same time, technically. The CLI shell respects per-session quotas in a way the OAuth path didn't. From Anthropic's side, those are different problems.

From your side, the lesson is the same as the original cutoff. Building your whole pipeline on one vendor's subscription pricing and being shocked when they change the rules has a name now. The $1,500/mo API gap versus the $20/mo subscription was never sustainable. Someone was always going to close it. Anthropic did, then partially undid, and there's no commitment that they won't do it again the next time the math swings.

The people who got hurt the worst weren't the ones running on the API. They were the ones whose entire setup assumed subscription access was permanent and whose agents started failing silently the morning of April 4. Don't be that person on the next swing.

Or just stop tracking the policy weather

On TryOpenClaw.ai, model routing is the default and you don't see any of this. Your interactive sessions go to whichever Claude tier we currently have provisioned. Background jobs route to cheap models with a hard budget cap. When Anthropic flips their stance again - and they will - your config doesn't change, because we're already pooling capacity across providers and accounts on the back end.

Flat $39/month. No JSON edits, no OAuth extraction debates, no 25-message ceiling. Just an agent that keeps running.