Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
anthropic claude reasoning
| Source: HN | Original article
Anthropic has sent a terse notice to all Claude Code subscribers: starting April 4 at 12 p.m. PT (20:00 BST) the company will block the use of its subscription tokens in any third‑party harness, including the popular OpenClaw IDE. The email, posted on Hacker News by user “firloop,” makes clear that the restriction applies to every Claude Code plan, effectively cutting off the integration that many developers have relied on to embed Anthropic’s code‑generation model into their own tooling.
The move is the latest escalation in a series of lock‑downs that began in January, when Anthropic first barred OAuth tokens for Claude Pro and Max plans from external applications, and was followed in February by a broader prohibition on third‑party IDEs. As we reported on Jan 11 2026, the company cited “security and compliance” concerns, but the suddenness of the April deadline has sparked fresh worries about vendor lock‑in and rising costs for teams that now must migrate to Anthropic’s native interface or seek alternative solutions.
For developers, the impact is immediate. OpenClaw, a community‑maintained wrapper that lets users invoke Claude Code from VS Code, JetBrains, and other editors, will stop functioning, forcing teams to rewrite build pipelines or pay for Anthropic’s own web‑based environment. The restriction also raises questions about the future of open‑source AI tooling, especially after the “Safety Layer” leak we covered on Apr 3, which showed how much of Claude’s functionality is hidden behind proprietary controls.
What to watch next: Anthropic’s response to the backlash on forums and social media, any legal challenges or regulatory scrutiny over anti‑competitive practices, and the emergence of rival code assistants—both from OpenAI and the growing open‑source LLM ecosystem—that promise unrestricted IDE integration. The next few weeks will reveal whether the policy shift reshapes the balance between proprietary AI services and the developer community’s demand for open, flexible tooling.
Sources
Back to AIPULSEN