Anthropic takes legal action against OpenCode

Original Article ↗ Hacker News Discussion ↗

Anthropic has pressured the open‑source coding agent OpenCode to remove support for using Claude Code subscription credentials, arguing that its discounted, subscription-based access is meant only for Anthropic’s own tools and not third‑party clients. Commenters debate whether this is a reasonable enforcement of terms of service and cost control for heavily subsidized tokens, or an anti-competitive move to lock users into Anthropic’s harness and data-collection pipeline. The episode fuels broader worries about model providers’ growing control over how their services are accessed, the fragility of open tooling built on proprietary APIs, and the contrast with competitors that tolerate or encourage third‑party clients.

What Anthropic Asked OpenCode To Do

  • Anthropic sent legal threats that led OpenCode to:
    • Remove support for using Claude Code subscription tokens via unofficial plugins.
    • Remove references, prompts, and code that imitated/leveraged Claude Code’s internal APIs.
  • Using Anthropic’s standard, pay‑per‑token API key with OpenCode is generally understood to still be allowed; the conflict is about using subsidized Claude Code access in third‑party harnesses.

Business Model & Subsidy Arguments

  • Many comments frame Claude Code subscriptions as heavily subsidized vs API pricing (estimates of ~90%+ discount if fully utilized).
  • Pro‑Anthropic view:
    • Subsidy is meant to drive adoption of Anthropic’s own harness (Claude Code), not third‑party tools.
    • Third‑party harnesses can’t or won’t optimize caching and routing (Haiku/Sonnet/Opus), making usage more expensive.
  • Critics counter:
    • If token limits exist, overuse is Anthropic’s problem, not the customer’s.
    • Subscription vs API pricing may be more about price discrimination and lock‑in than true costs.

Legal Basis Debated

  • Several commenters cite:
    • Terms of Service violations by users (using Claude Code subs outside allowed contexts).
    • Possible “tortious interference” by OpenCode for facilitating ToS breaches.
  • Others argue:
    • OpenCode itself hasn’t agreed to Anthropic’s ToS and is only publishing code (raised as potential “code as speech” issue).
    • The legal threat may rely more on power asymmetry and litigation costs than on clearly settled law.
  • Exact strength of Anthropic’s legal position is described as unclear.

Competition, Lock‑in, and Open Source

  • Many see this as an attempt to:
    • Protect Anthropic’s “moat” by tying discounted tokens to its own client.
    • Capture telemetry and reinforcement signals from Claude Code that third‑party harnesses can’t provide.
    • Prevent easy switching between models/providers inside neutral tools like OpenCode.
  • Prior disputes (e.g., over a similarly named tool) and Anthropic’s acquisition of Bun increase fears about future control over OSS dependencies and trademarks.

User Sentiment & Alternatives

  • Strong negative reaction: accusations of hypocrisy (given training data practices), hostility to users, and anti‑competitive behavior.
  • Some defend Anthropic as acting like any rational business protecting a loss‑leading product.
  • Multiple commenters say they’ve switched or will switch to alternatives (OpenAI/Codex, GPT 5.x, Gemini, Kimi, Chinese models, open‑weight models, other agents like Pi).
  • Broader worries about enshittification, proprietary harness lock‑in, and calls for regulation ensuring third‑party client rights.