Anthropic Explicitly Blocking OpenCode

Core dispute: private vs public access

• Anthropic is blocking use of Claude Code subscription endpoints by OpenCode, while leaving the metered public API fully available.
• Defenders say Claude Code is a private, subsidized API never sold as general-purpose; OpenCode reverse‑engineered OAuth and hijacked that channel, so blocking is straightforward ToS enforcement.
• Critics argue the blocking is tool‑specific: the gist shows “You are OpenCode” being singled out in system prompts, while other tool names pass, which looks like selective enforcement and an attempt to protect a walled garden.

Pricing, utility analogies, and antitrust concerns

• Many see a huge arbitrage: Claude Pro/Max via Claude Code is dramatically cheaper per token than the public API.
• Some frame this as basic market segmentation: flat‑rate product (Claude Code) vs pay‑per‑use API, with the former optimized and cross‑subsidized (unused capacity, caching, client‑side control).
• Others call it predatory pricing or anti‑competitive: a below‑cost subscription to entrench Claude Code and starve third‑party tools that can’t match subsidies.
• Utility and telco analogies recur (water service, sprinkler lines, AT&T phones, Comcast bundles) alongside arguments that LLMs should be regulated like utilities/common carriers.

Security, reliability, and technical details

• OpenCode is criticized for a recent unauthenticated RCE, seen by some as evidence of poor security practices; others note Claude Code has also shipped breaking bugs and is partly “AI‑generated.”
• Several say any coding agent is effectively an RCE and should always run in a sandbox/VM.
• There’s discussion of using ACP/Claude Agent SDK or wrapping Claude Code directly instead of reusing auth tokens, but people note limitations for fine‑grained orchestration.
• Speculation about a “cat and mouse” future includes model attestation or hidden shibboleths to enforce tight coupling between client and endpoint.

User reactions and philosophy

• Some cancel Claude Max and move to competitors that explicitly allow third‑party harnesses; others think this is overblown or performative.
• One camp views adversarial interoperability and working around blocks as core hacker ethos; another emphasizes “break ToS, get banned, don’t complain.”
• Broader concern: this fits a pattern of platforms using pricing, telemetry, and closed clients to lock in users and resist open, user‑controlled tooling.