Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw

Hacker News Discussion ↗

Policy change & what it covers

  • Anthropic is blocking use of Claude Code subscription quotas with “third‑party harnesses” like OpenClaw / OpenCode; such use must now be paid via extra usage or API.
  • Change appears targeted at automated, high‑duty agent workflows rather than occasional CLI/editor scripting, but boundaries (e.g., claude -p, ACP, custom scripts) are widely viewed as unclear.
  • Only some accounts received emails (likely based on detected usage), though anyone can claim the extra-usage credit via the usage page.

Economics, capacity, and fairness

  • Many argue this is about unsustainable unit economics: subscriptions are heavily subsidized, priced for human, bursty use; 24/7 agents can max quotas and cost more than they pay.
  • Others reply that users bought “limits” and should be able to spend them however they want; if it’s too costly, Anthropic should adjust prices/limits instead of banning specific usage.
  • Several note Anthropic’s capacity constraints and frequent rate‑limits/outages; they see cutting OpenClaw as prioritizing enterprise and “normal” Claude Code users.
  • Some see it as self‑preferencing and ecosystem control rather than pure capacity management.

User impact & reactions

  • Heavy Claude Code users already hit 5‑hour and weekly limits quickly; OpenClaw often exhausted quotas even faster.
  • Some plan to downgrade or cancel Anthropic subscriptions, move agentic work to other providers or local models, and keep Claude only for light interactive use.
  • Others welcome the change, saying OpenClaw‑style workloads degraded service for regular users and that subsidizing a “shadow API” was never the deal.

Alternatives & workarounds

  • Many mention switching coding/agent workflows to OpenAI Codex (which currently allows third‑party harnesses), Chinese providers (GLM, Minimax, StepFun, Kimi), GitHub Copilot, or editor‑integrated tools.
  • There is strong interest in open‑source models (Gemma 4, Qwen, local MoE models) plus rented or local GPUs as a way to escape vendor limits and lock‑in, despite lower quality vs. Sonnet/Opus.

Trust, lock‑in, and future direction

  • Some see this as a bait‑and‑switch: terms were tightened after people built workflows on top of subscriptions.
  • Others counter that ToS always disallowed automated non‑Anthropic clients and that Anthropic is acting reasonably by enforcing them.
  • Broader concern: agentic/autonomous usage doesn’t fit human‑oriented subscriptions; many expect a long‑term shift toward pure API billing or local/open models for agents.