OpenClaw on Your $20 Claude Sub After Anthropic Banned It

OpenClaw’s bundled claude-cli backend is officially sanctioned by Anthropic. OAuth-token extraction tools stay blocked. The carve-out works because shelling out to claude -p preserves prompt caching, so a $20 Pro or $200 Max sub routes through OpenClaw without four-figure API bills. The catch used to be a 5-hour usage cap. From June 15, 2026, that claude -p traffic moves onto a separate monthly Agent SDK credit, so the real limit is now a modest dollar budget.

What Changed in Anthropic’s Third-Party Tool Policy?

Most users found out about the policy change when their Anthropic bill jumped, not from a press release. Heavy agentic workflows once billed against a flat Pro or Max subscription . Then Anthropic forced third-party orchestrators onto the pay-per-token API, and those same workflows tracked toward $1,500 a month on Opus 4.6. The original concern was narrower than the community read it as. Anthropic’s target was one specific class of tool. It extracts the OAuth token from a local Claude Code install and calls the Anthropic API directly under that identity. That pattern skips Anthropic’s prompt caching. It pushes load to the API tier without the caching benefit Anthropic gets when Claude Code runs the request itself.

The opposite path took weeks to surface. Shelling out to the local claude binary is fine, because Claude Code itself handles the auth and caching the way Anthropic wants it. The PSA that finally made this clear came from the r/openclaw “you can still use your $20/mo sub” thread (194 comments). The OP framed the cost gap directly:

If you run heavy agentic workflows like I do, you probably watched your monthly bill skyrocket, I was on track to hit over $1,500 a month just running Opus 4.6.

u/mehdiweb (OP, r/openclaw PSA thread)

Comments in the thread point to Boris Cherny’s X threads as the Anthropic-side confirmation. They also cite OpenClaw GitHub issue #66874 as the implementation log. The wording is worth a second look. When this post first ran, “sanctioned” rested on OpenClaw’s docs page and Anthropic staff statements, not a published policy. That has since firmed up. Anthropic now has an official Help Center policy that covers programmatic claude -p and Agent SDK usage, detailed in the next section. It is still not a lawyer-grade contract. The policy can be modified or discontinued, so compliance-bound readers should treat it as firm guidance, not a binding term. Migration-curious readers should also weigh OpenClaw vs Hermes on the memory question before committing to either gateway.

How OpenClaw’s claude-cli Backend Works Under the Hood

The reason the workaround is allowed is that nothing about the request looks different from interactive Claude Code use. The detail lives in the OpenClaw CLI backends documentation :

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.

OpenClaw (per the same docs page)

Mechanically, OpenClaw spawns the claude binary with a session id. It keeps that Claude stdio process alive for the whole OpenClaw session and streams follow-up turns over stream-json stdin. Output gets parsed as JSON or plain text. The session id persists per backend, so later turns in the same chat reuse the long-lived subprocess. That is why the first message in a session feels slow and turn 2 onward is near-instant: the stdio handshake happens once.

Skills delegation is the other piece worth knowing about. OpenClaw passes its skills catalog two ways at once. First, a compact summary appended to the system prompt. Second, a temporary Claude Code plugin via --plugin-dir that holds only the skills eligible for that agent and session. Claude Code’s native skill resolver sees the same filtered set OpenClaw would otherwise advertise. So the behavior is consistent whether you trigger a skill from inside Claude Code or through OpenClaw.

The /think mapping is the last surface detail. OpenClaw’s minimal and low levels map to Claude’s --effort low, adaptive and medium map to medium, and high, xhigh, and max map directly. Any other CLI backend you wire in (Codex, Gemini CLI) needs its owning plugin to declare an equivalent argv mapper, otherwise the level just falls through.

How To Route OpenClaw Through Your Claude Pro Subscription

The full setup is three commands and a config sanity check. One prerequisite: Claude Code must already be installed and logged in on the same host where OpenClaw will run. The bundled backend depends on claude being on $PATH and on a valid Claude Code identity.

The first message you send after setup round-trips through a freshly spawned claude process. That costs a few seconds while the stdio handshake completes. Every later message in the same session reuses the same subprocess. Latency then drops to about the network round-trip plus Anthropic’s own response time. That drop is how you know the session id is being reused, not a fresh API call going out each turn.

What the June 15, 2026 Agent SDK Credit Changes

The CLI workaround stopped being a gray area on June 15, 2026. Anthropic’s Help Center article on using the Agent SDK with your plan introduced a separate monthly Agent SDK credit for subscription plans. It covers exactly the path OpenClaw uses.

The credit is denominated in dollars of API-equivalent usage and refreshes every month:

It applies to Agent SDK projects , the claude -p non-interactive command, the Claude Code GitHub Actions integration, and third-party apps authenticated through your subscription via the Agent SDK. OpenClaw’s claude-cli backend is the claude -p path, so it qualifies on both counts. The subscriber email announcing the change spelled out the consequence:

As part of this change, Agent SDK and other programmatic usage will run on this credit, and will not impact your subscription limits. This includes third-party applications built on the Agent SDK.

Anthropic (subscriber email announcing the June 15 change)

This is the part that changes the cron math. Before June 15, every OpenClaw turn drew down the same interactive allowance as your chat and Claude Code sessions. Now claude -p traffic drains the Agent SDK credit first. The 5-hour interactive cap stays reserved for Claude Code, Claude Cowork, and chat. The credit is per-user and not pooled across a team. It does not roll over, and it needs a one-time opt-in. Subscribers get a redemption notice in June. Once the credit is spent, continued use draws from pay-as-you-go extra usage, which you turn on or off manually. If it is off, requests pause until the next monthly refresh.

The fine print is worth reading before you lean on it. The arrangement is subject to terms posted when the claim flow opens. The credit has no cash value and is non-transferable. Anthropic also reserves the right to modify or discontinue it.

Why Cron Jobs Still Need a Cheaper Backend

Before June 15, the 5-hour Pro and Max usage cap was the rate limit the workaround did not solve. The PSA thread spelled it out:

Your Pro/Max plan is not unlimited. It has a finite usage cap (usually 5 hours), and if you route all your automated background cron jobs through it, you will hit that cap in 10 minutes and your agent will die.

u/mehdiweb (same OP, on the 5-hour cap)

The Agent SDK credit moves that wall, it does not remove it. Cron-driven claude -p traffic now drains the monthly credit instead of the interactive cap. But the credit is small and priced like the API. The same OP was on track for $1,500 a month of Opus usage. A $20 Pro credit, or even a $100 Max 5x credit, covers only a fraction of that before pay-as-you-go extra usage kicks in. So the hybrid stack still pays off, just measured against a dollar budget rather than a clock.

The split the community converged on goes by intent. Interactive planning, debugging, and chat sessions that need Opus 4.7 quality stay on the CLI backend. Everything cron-driven, scheduled, or batch routes to a cheaper plan with its own quota. If your scheduled workload is light, a single Anthropic identity may cover it. In that case, Claude Code’s own scheduled tasks and /loop can absorb cron-style jobs without an extra backend. The most-cited options on r/openclaw are:

Z.ai’s pricing is the closest near-Claude option. The GLM Coding Plan Lite costs $18 a month. It exposes GLM-5.1, GLM-5-Turbo, GLM-4.7, and GLM-4.5-Air through an Anthropic-compatible API. GLM-5.1 scored 58.4 on SWE-Bench Pro. It also reached 94.6% of Claude Opus 4.6’s score on the internal Claude Code eval. That is close enough that cron-driven refactors and code review rarely notice the swap.

One anti-pattern is worth calling out by name: letting OpenClaw self-repair its broken Docker image. The PSA thread documented users burning through $50 of tokens watching the agent recursively break its own install. OpenClaw founder Peter Steinberger acknowledged the broken Docker image and the broader regression in the “rough week” post-mortem :

The trouble started around 2026.4.24. By 2026.4.29 it was obvious enough that nobody could pretend this was just a few weird installs. Gateways got slower. Some installs got stuck in plugin dependency repair loops.

Peter Steinberger (OpenClaw founder, post-mortem)

The newer 2026.5.5 and 2026.5.7-beta.1 releases harden the gateway container. They drop the NET_RAW and NET_ADMIN capabilities and add no-new-privileges in the bundled docker-compose.yml. They also ship pre-built images at the GitHub Container Registry. If you pin a Docker tag, pin the explicit version (2026.5.5) rather than latest. Verify any :latest rollout by hand before letting an agent loose on it.

When NOT To Use This

• You don’t have Claude Code installed on the same host where OpenClaw runs. The bundled backend depends on the local claude binary and a logged-in Claude Code identity; without both, the login command fails immediately.
• Your workload is mostly automated cron jobs. They will exhaust the monthly Agent SDK credit ($20 Pro, $100 Max 5x, $200 Max 20x) before doing useful work. A pay-per-token API or a $18 GLM plan is cheaper at sustained volume and survives quota resets.
• You require a fully durable, unchangeable Anthropic policy guarantee. The June 15 Agent SDK credit is an official published policy. That is a real upgrade over staff statements. But Anthropic can still modify or discontinue it, so compliance, audit, and regulated industries should treat the arrangement as subject to change.
• You are already on a custom enterprise Anthropic plan with negotiated rate limits. The API path is usually cheaper than the CLI roundabout once volume discounts kick in.
• You run OpenClaw on a multi-tenant host where a single Claude Code identity would be shared across users. The CLI backend has no concept of per-user attribution; everyone in the shared install bills against the same claude auth session.

FAQ