onemanopsBook a call
openclawclaudeanthropicsecurityoauth

Anthropic Just Locked the Front Door on OpenClaw Users - Here's How to Get Back In

Anthropic no longer lets OpenClaw use your Claude subscription for access. You now need a separate API key from Anthropic's developer console. The switch takes about ten minutes, costs per-use instead of a flat monthly r

April 14, 20263 min readBy AndresUpdated April 14, 2026

Anthropic cut off subscription-based Claude access for OpenClaw on April 4, 2026. If you're running OpenClaw with Claude and it stopped working, you're not alone - and the fix takes about ten minutes.

TL;DR: Anthropic no longer lets OpenClaw use your Claude subscription for access. You now need a separate API key from Anthropic's developer console. The switch takes about ten minutes, costs per-use instead of a flat monthly rate, and changes how your credentials are stored. Here's the step-by-step.

What Actually Changed?

Before April 4, OpenClaw connected to Claude through your Anthropic subscription. You logged in, it worked. That connection - called OAuth - meant Anthropic handled all the credential management behind the scenes.

Boris Cherny, a Claude Code executive, announced that third-party tools like OpenClaw would no longer be covered under subscription plans. Now, if you want Claude powering your OpenClaw setup, you need to go through Anthropic's API using a dedicated key.

Here's the thing. This isn't a bug or a temporary glitch. This is Anthropic drawing a line between their own products and everything else. OpenClaw creator Peter Steinberger said it directly: "It's gonna be harder in the future to ensure OpenClaw still works with Anthropic models."

So the old way is gone. The new way works - it just requires a different kind of setup.

How Do You Set Up an API Key?

Here's what you're gonna do:

  1. Go to console.anthropic.com. Create an account if you don't have one, or sign into your existing Anthropic account. This is separate from your Claude chat subscription.

  2. Navigate to API Keys. Look for the API Keys section in your dashboard. Click "Create Key." Give it a name you'll recognize - something like "openclaw-home" works fine.

  3. Copy the key immediately. Anthropic only shows it once. If you lose it, you'll need to create a new one. Paste it somewhere safe for the next step.

  4. Open your OpenClaw settings. In your OpenClaw instance, find the credentials or AI provider configuration section. Replace the old authentication method with your new API key. The exact location depends on your OpenClaw version, but it's typically under Settings > AI Provider or Credentials.

  5. Test the connection. Send a simple message through OpenClaw to confirm Claude responds. If it works, you're done.

The whole process is about ten minutes if nothing goes wrong.

What Does This Mean for Your Security?

Now, here's where most guides stop - and where it actually matters.

Under the old system, Anthropic managed your credentials. You never saw a key, never stored one. Under the new system, you hold the key. That key is a direct line to your Anthropic account and your billing.

Think of it kind of like the difference between using your face to unlock your front door versus carrying a physical key. The physical key works great - until someone copies it. If your OpenClaw instance is compromised, that API key can be used to run up charges on your account.

Three things to do right now: keep your OpenClaw installation updated to the latest version, never share your API key in screenshots or public configs, and set a monthly spending limit in your Anthropic console under billing settings.

That's the mechanical fix. But the bigger picture - what it means that Anthropic is deliberately distancing itself from the tool 330,000 people use every day - that's a conversation we're about to have.

Related posts