Anthropic Cut Off Claude for OpenClaw — Here's What Still Works

A post on r/openclaw this week (96 upvotes in 24 hours) surfaced what a lot of people are quietly hitting: Anthropic has restricted subscription-tier Claude access for third-party harnesses like OpenClaw. If your setup uses a Claude subscription (Max, Pro, or Teams) rather than a direct API key, you may have already lost access — or will soon.

Here's what's happening, what still works, and how to keep your OpenClaw setup running on Claude.

What Changed

Anthropic has tightened which applications can access Claude through the subscription tier. Previously, OpenClaw could authenticate using session tokens from a Claude.ai account. Anthropic has moved to restrict this — only officially sanctioned API clients (including Claude Code CLI) retain subscription-level access.

Current Status by Access Method

Option 1: Switch to Anthropic API Key (Recommended)

This is the cleanest fix. Sign up for Anthropic API access and use a real API key instead of a session token.

1. Go to console.anthropic.com → Create an account or log in
2. Go to API Keys → Create new key
3. Add a small credit balance ($5–$10 to start)
4. Set a spending limit — go to Settings → Limits and cap it at $20–$50/month
5. In your openclaw.json, update the Anthropic provider to use "apiKey": "sk-ant-..."
6. Restart OpenClaw

Option 2: Use the Claude Code CLI Proxy (The Loophole)

The r/openclaw post that went viral this week spotted something: Claude Code CLI still has full subscription access — and it can be configured to act as a local API proxy. This lets OpenClaw route requests through the Claude Code CLI process, which retains subscription-tier access.

This is a workaround, not a permanent solution. Anthropic may close it. But as of today it works:

# Install Claude Code CLI if you don't have it
npm install -g @anthropic-ai/claude-code

# Start the local proxy (keep this running)
claude --proxy-port 8090

# In openclaw.json, point Anthropic to the local proxy
{
  "providers": {
    "anthropic": {
      "baseUrl": "http://localhost:8090/v1",
      "apiKey": "proxy"
    }
  }
}

Option 3: Switch to a Different Model

If you don't want to set up billing right now, OpenClaw works well with several free or cheaper alternatives:

• Google Gemini 2.5 Flash — Fast, cheap, generous free tier. Good for most daily tasks.
• Ollama + Qwen 3.5 9B — Completely free, runs locally, no API calls. Performance is lower than Claude but zero cost.
• OpenAI GPT-4o mini — Inexpensive, widely available, solid performance for task automation.

To switch default model in openclaw.json:

{
  "defaultModel": "google/gemini-2.5-flash",
  // or: "ollama/qwen3.5:9b"
  // or: "openai/gpt-4o-mini"
}

What We Recommend

For anyone running OpenClaw as a serious business tool:

1. Get an Anthropic API key now — it's the stable, supported path. The cost is reasonable and you keep Claude.
2. Set a hard spend limit immediately — before anything goes live. $30–$50/month cap protects you from surprises.
3. Add Ollama as a fallback — local model for heartbeat and low-stakes tasks cuts your API bill significantly.

Why This Keeps Happening

Anthropic, OpenAI, and Google are all gradually tightening which access methods work with third-party tools. This is partly about enforcing terms of service, partly about managing compute costs, and partly about pushing developers toward paid API tiers where usage is metered and controllable.

The practical implication for OpenClaw users: direct API keys are always more stable than session token tricks. Every workaround that relies on unofficial access eventually gets closed. Building your setup on proper API keys is the only reliable long-term path.

This is also why managed care matters — when these changes happen, you need someone tracking them and reconfiguring your setup before you lose access mid-week. Our managed care clients were notified about this change within 24 hours of it surfacing.