Anthropic's Walled Garden: The Claude Code Crackdown

## What Happened Anthropic deployed “strict new technical safeguards” blocking subscription OAuth tokens from working outside their official Claude Code CLI. Tools like OpenCode had been spoofing the Claude Code client identity, sending headers that made Anthropic’s servers think requests came from the official tool. That stopped working overnight. > Yesterday we tightened our safeguards against spoofing the Claude Code harness after accounts were banned for triggering abuse filters from third-party harnesses. > — Thariq Shihipar, Anthropic … - **OpenAI employees**: Already blocked in August 2025 for using Claude to benchmark GPT-5. - **Anyone using subscription OAuth outside Claude Code**: If you weren’t using the official CLI, you got locked out. What still works Standard API keys still function. OpenRouter integration still works. The block specifically targets subscription OAuth tokens being used in third-party harnesses. If you’re paying per-token through the API, you’re unaffected. … ## The Backlash > Seems very customer hostile. > — DHH (creator of Rails) Users who’d invested in OpenCode workflows found themselves locked out mid-project: > Using CC is like going back to stone age. I immediately downgraded my $200/month Max subscription, then canceled entirely because it was unusable for the workflows I have. > — @Naomarik on GitHub … ## The Bigger Picture This isn’t just about OpenCode. Anthropic also cut off: - **xAI via Cursor**: Competitors can’t use Claude to build competing products - **OpenAI (August 2025)**: Blocked for benchmarking GPT-5 with Claude The pattern is consolidation. Anthropic wants you in their ecosystem, using their tools, on their terms. The open source models targeting Claude Code compatibility suddenly look more strategic.