Claude Code users: OpenClaw is dead, here's your 60-second migration
If you're seeing this, you probably already know: Anthropic has blocked Claude Code subscriptions from routing through OpenClaw. And if OpenClaw CVE-2026-33579 (privilege escalation) wasn't enough reason to move on, now you have no choice.
Here's the migration in 60 seconds.
What OpenClaw was doing
OpenClaw sat between Claude Code and Anthropic's API, acting as a local proxy. Developers used it to:
- Pool requests across team members
- Remove per-user rate limits
- Add custom middleware
All of this is still possible. You just need a proxy that Anthropic hasn't banned.
The 60-second migration
# Step 1: Stop OpenClaw (it's blocked anyway)
pkill openclaw # or however you started it
# Step 2: Point Claude Code at a compliant proxy
export ANTHROPIC_BASE_URL=https://api.simplylouie.com
# Step 3: That's it. Claude Code works now.
claude "fix the tests in src/"
Your existing Claude Code subscription handles authentication. The proxy handles the rest.
Why ANTHROPIC_BASE_URL is the right approach
OpenClaw used a local server that intercepted traffic at the network layer. That's why it got the CVE — privilege escalation is a natural risk when you're running a local privileged server.
ANTHROPIC_BASE_URL is the official mechanism Claude Code exposes for proxy configuration. It's documented, intentional, and supported. Anthropic can't block it without breaking their own docs.
# Permanent setup (add to ~/.bashrc or ~/.zshrc)
export ANTHROPIC_BASE_URL=https://api.simplylouie.com
# Verify it works
claude --version
claude "hello, are you routing through the proxy?"
What you get vs what you lose
| Feature | OpenClaw | ANTHROPIC_BASE_URL proxy |
|---|---|---|
| Rate limit removal | ✅ | ✅ |
| Team request pooling | ✅ | ✅ |
| Anthropic compliant | ❌ (now banned) | ✅ |
| CVE-free | ❌ CVE-2026-33579 | ✅ |
| Local server required | ✅ (attack surface) | ❌ |
| Works today | ❌ (blocked) | ✅ |
The rate limit problem, solved
If you were using OpenClaw specifically to avoid Claude Code's rate limits during long sessions, here's what the proxy actually does:
# Without proxy: Claude Code hits Anthropic's rate limits directly
# You get: "Rate limited. Please wait X minutes."
# With ANTHROPIC_BASE_URL proxy: requests route through a pooled endpoint
# You get: uninterrupted sessions
export ANTHROPIC_BASE_URL=https://api.simplylouie.com
claude "refactor the entire auth module, run tests after each file"
# No rate limit interruptions
The proxy costs ✌️$2/month at simplylouie.com — less than a coffee.
For teams
If your team was using OpenClaw for shared rate limits, the setup is the same — each developer sets their own ANTHROPIC_BASE_URL:
# Add to your team's .envrc or onboarding docs
export ANTHROPIC_BASE_URL=https://api.simplylouie.com
# Or in your project's .env (don't commit this)
ANTHROPIC_BASE_URL=https://api.simplylouie.com
Each developer has their own account. No shared credentials, no privilege escalation risk, no CVEs.
The longer answer
OpenClaw's architecture was always fragile. A local privileged server that intercepts traffic between a CLI tool and an external API is exactly the kind of thing that gets CVEs. The ban just accelerated the inevitable.
ANTHROPIC_BASE_URL is cleaner:
- No local server
- No privileged process
- No attack surface
- One env var
If you're building on Claude Code for any length of time, you want your toolchain to be stable. A cloud proxy that uses the official extension mechanism is stable. A local server that Anthropic bans is not.
Quick reference
# Temporary (current session only)
export ANTHROPIC_BASE_URL=https://api.simplylouie.com
# Permanent
echo 'export ANTHROPIC_BASE_URL=https://api.simplylouie.com' >> ~/.zshrc
source ~/.zshrc
# Verify Claude Code is using it
env | grep ANTHROPIC
# Should show: ANTHROPIC_BASE_URL=https://api.simplylouie.com
OpenClaw is done. One env var and you're back to work.
SimplyLouie is an Anthropic-compliant Claude proxy at ✌️$2/month. Try it free for 7 days.
Top comments (0)