Anthropic Locked OpenClaw Out. Model Routing Became the Only Rational Response
A tweet from Peter Steinberger sparked hope that Claude was back for OpenClaw users. It wasn’t. What actually happened is more important: the Anthropic cutoff forced the community to build resilience that should have existed from day one, and model routing went from cost optimization to survival infrastructure.
Why this matters
If you run an agent stack that depends on a single LLM provider, the April 4 Anthropic cutoff is your warning shot. The community response, the workarounds, and the OpenClaw v4.3 release that followed all point to the same conclusion: multi-provider model routing isn’t optional anymore. Here’s what happened, what changed, and what your setup should look like now.
The timeline: what actually happened on April 4
A tweet from Boris Cherny, head of Claude Code, seemed to confirm that “CLI-style usage” of Claude through OpenClaw was permitted. OpenClaw scrambled to add support. Then subscription-backed OAuth tokens started returning 401 errors. The “permission” lived in a tweet, not in Anthropic’s enforcement layer.
As u/siberianmi put it: “It’s in a weird limbo where CLI use should work in theory but doesn’t in practice.”
The original Reddit post by u/RuleGuilty493 caught flak for misreading the source. Steinberger’s tweet said the official Claude Code CLI remains within subscription scope. Third-party harnesses being re-admitted was never on the table. These are fundamentally different things.
On April 4, 2026 at 12pm PT, Anthropic flipped the billing switch. Third-party tools routing through Claude subscription OAuth were no longer covered by Pro, Max, or Team plans. Cherny’s explanation was blunt: “Our systems are highly optimized for one kind of workload, and to serve as many people as possible with the most intelligent models, we are continuing to optimize that.”
The economic logic was clear before the policy. A $200/month Max subscription could generate $1,000+ in API-equivalent token consumption when driven by an autonomous agent running 24/7. OpenClaw users were arbitraging Anthropic’s subscription pricing at scale. The speed limit that made flat-rate pricing viable was bypassed entirely by continuous agent loops.
What’s still allowed:
- The official Claude Code CLI, including via SSH
- Claude.ai and Cowork
- Any third-party tool authenticating with an API key (pay-as-you-go)
- The ACP bridge through Claude Code CLI (as of April 2026, though Anthropic could close this at any point)
What’s blocked: routing subscription OAuth tokens through anything other than Anthropic’s own binaries. The enforcement is technical, not just legal. Anthropic deployed server-side client identity verification.
Model routing: from nice-to-have to survival skill
Before April 4, model routing in OpenClaw was an optimization. After April 4, it became infrastructure.
u/Temporary-Leek6861 nailed the argument:
“If Anthropic can shift the enforcement story in a single tweet, they can shift it back just as quickly. And the bigger reason for multi-provider isn’t the Anthropic drama at all: Claude had 4 separate outages in April (10th, 13th, 15th, 16th). The infra is strained.”
Their setup: GLM-5.1 as primary with Sonnet as fallback via BetterClaw. 85% of routine tasks go to GLM, only 15% need Claude. That’s not ideology, that’s cost engineering.
Since the Reddit thread: OpenClaw v4.3 shipped the Multi-Provider Engine. Released April 14, this was the direct engineering response to the April 4 cutoff. The key changes:
- Unified provider routing via
providers.toml: one config file defining every model endpoint (Anthropic, OpenRouter, GLM-5.1, Gemini, Ollama, vLLM, anything OpenAI-compatible) - Fallback chains: set a primary and up to two fallbacks per agent. Rate-limited or down? Requests flow to the next provider without dropping the session
- Per-provider budget caps: hard ceilings in dollars or tokens per day/week/month. When you hit the cap, the agent switches providers instead of burning through your card
- Reasoning-trace billing fixes: thinking tokens now accounted separately from response tokens, matching how Anthropic and Google actually bill
The old llm config block is gone. Setups that relied on the Claude subscription adapter don’t auto-migrate. You have to write a new providers.toml by hand and reboot.
BetterClaw’s benchmark data supports the Reddit users’ instinct: routing heartbeats to Haiku, sub-agents to Sonnet, and only the primary reasoning chain to Opus cuts API costs by 50-65%. With the new v4.3 provider engine, this is now a first-class config pattern instead of a hack.
The community response: exit or adapt
The reactions split into two camps:
- u/desexmachina: “Fool me once, shame on you. Kimi 2.6 is quite smart, bye Opus.”
- u/Sea_Taste_9122: Migrated to
claude -pfor crons, no intention of returning to the OpenClaw integration - u/jake_2998e8: “We reacted appropriately, found workarounds and alternatives. Claude is not the only player in town. They definitely felt the needle move.”
Peter Steinberger himself, OpenClaw’s creator, joined OpenAI in February 2026 and moved his own agent workflow to Codex OAuth. Twelve parallel agents on a $200/month plan. The symbolism writes itself.
For the technically inclined
From here on, this gets into configuration details and billing architecture. If you just care about the takeaway, skip to the conclusion.
How client identity verification works
Anthropic’s enforcement isn’t a terms-of-service change. It’s a server-side check that verifies the client binary making the request matches an authorized binary. OAuth tokens issued to Max or Pro subscriptions are tied to a specific client identifier. When a third-party tool presents that token, the server rejects it because the client fingerprint doesn’t match.
This means there’s no configuration workaround within OpenClaw. The token itself is valid, but the context in which it’s presented isn’t authorized. The only paths forward are:
- Use the official Claude Code CLI directly (supports ACP)
- Use API keys with pay-as-you-go billing
- Route to alternative providers entirely
What the v4.3 providers.toml looks like
The new config replaces the old llm block with a provider-first architecture:
[providers.anthropic]
type = "anthropic"
apiKey = "${ANTHROPIC_API_KEY}"
budgetCap = { daily = 10.00 }
[providers.openrouter]
type = "openai-compatible"
baseUrl = "https://openrouter.ai/api/v1"
apiKey = "${OPENROUTER_API_KEY}"
budgetCap = { weekly = 50.00 }
[agents.primary]
provider = "openrouter"
model = "minimax/minimax-m2.5"
fallback = ["anthropic:claude-sonnet-4", "ollama:glm-5.1"]
[agents.coder]
provider = "anthropic"
model = "claude-sonnet-4"
fallback = ["openrouter:minimax/minimax-m2.5"]
budgetCap = { monthly = 200.00 }
Each agent gets a primary provider and up to two fallbacks. Budget caps are per-provider, not global. When a provider hits its cap or returns a rate-limit error, the request flows to the next provider in the chain without dropping the session.
The cost math behind routing
BetterClaw’s data on a typical 8-hour agent session:
| Pattern | Cost (API equiv.) | Savings vs. Opus-only |
|---|---|---|
| Opus for everything | $4.80 | baseline |
| Heartbeats → Haiku, sub-agents → Sonnet, reasoning → Opus | $1.68-2.40 | 50-65% |
| GLM-5.1 primary, Sonnet fallback | $0.72-1.20 | 75-85% |
The last pattern is what u/Temporary-Leek6861 described. It works because 85% of agent interactions don’t need frontier-model reasoning.
The point
Key points:
- Subscription-backed Claude access through third-party harnesses is blocked and enforced at the billing layer. The official CLI and API keys still work.
- Model routing shifted from cost optimization to resilience infrastructure after April 4. Single-provider agent stacks are fragile by construction.
- OpenClaw v4.3’s Multi-Provider Engine makes fallback chains and budget caps first-class config, no longer a hack.
Whether the failure mode is a policy change, a billing enforcement, or a four-outage month on strained infrastructure, the result is the same: your agent goes dark. Model routing used to be about saving money. Now it’s about staying online.
🔗 Resources
- Peter Steinberger’s tweet - The original post that sparked the discussion
- Boris Cherny’s policy announcement - The actual April 4 enforcement statement
- The Register: Anthropic closes door on subscription use of OpenClaw - Best journalism coverage of the policy change
- Kersai: Full Workaround Guide - Comprehensive post-cutoff playbook
- BetterClaw: Model Routing Config - The 65% cost reduction setup
- OpenClaw April 2026 Release Notes - v4.3 Multi-Provider Engine details