Why did Anthropic ban OpenClaw creator Peter Steinberger?

Anthropic cited suspicious activity on his account. The ban came shortly after Anthropic changed pricing so Claude subscriptions no longer cover third-party harness usage like OpenClaw.

Was Peter Steinberger permanently banned from Claude?

No. The ban was temporary and was lifted shortly after. Anthropic later clarified that OpenClaw-style CLI usage is permitted.

What did Peter Steinberger say about the ban?

He posted that timings were suspicious - Anthropic first copied popular features into their closed harness (Claude Cowork), then locked out the open-source alternative.

Can OpenClaw still use Claude API after the ban?

Yes, but users must pay separately via API usage. Claude Pro and Max subscriptions no longer cover third-party harness usage as of April 4 2026.

How did the developer community react to the ban?

It sparked debate about open-source dependence on proprietary APIs and the power dynamics between AI labs and the tools ecosystem built on top of them.

← Back to dashboard

clawsmith.com/signal/anthropic-bans-openclaw-creator-steinberger-claude-access

⚠ IssueWide OpenLive

Anthropic Temporarily Bans OpenClaw Creator Peter Steinberger From Claude After Pricing Dispute

Anthropic suspended Peter Steinberger, creator of the 363K-star OpenClaw project, from accessing Claude API after pricing changes meant subscriptions no longer cover third-party harness usage. Steinberger accused Anthropic of copying OpenClaw features into Claude Cowork before locking out the open-source project. Ban was later lifted.

Product Idea from this Signal

A local proxy that detects provider policy blocks and censorship in real time and reroutes OpenClaw LLM requests to an alternative provider before the user sees a failure

51 ▲

Anthropic banned Claude subscriptions for OpenClaw on April 4, 2026, leaving thousands of users facing 50x cost increases overnight. Reports followed that Claude may also be censoring OpenClaw-related prompts. Existing routers like OpenRouter and LiteLLM handle cost-based routing and model failover, but none detect policy-level blocks (subscription enforcement, topic censorship, rate-limit discrimination against agent traffic) and reroute specifically around them. This proxy sits between OpenClaw and any LLM provider, fingerprints policy failures distinct from normal errors, and switches providers within the same conversation turn so the agent never stalls.

CLIOPEN-SOURCEPROXYDEVTOOLPROVIDER-ROUTING

CompetitiveView Opportunity →