Article by **Paul Sawers** published in **The New Stack** on **June 16, 2026**, on **Anthropic's suspension** — *« on the very day it was scheduled to go live »* — of the billing split that was to separate **Agent SDK** usage from Claude subscription limits. **Anthropic's message, quoted**: *« We're pausing the changes to Claude Agent SDK usage described below. For now, nothing has changed. »* **The article's contribution is not the announcement itself but the surrounding context**, in three circles. **Circle 1 — Anthropic's week**: on June 9, the release of **Fable 5 and Mythos 5**, the first generally available Mythos-class models with hardened cybersecurity safeguards; a few days later, a **US government export-control directive** forces Anthropic to **withdraw both models for all its customers worldwide**. The pricing suspension is read as *« a little good news »* in this context. **Circle 2 — the collateral damage of the timing**: companies that had already passed the change on to their own customers find themselves caught out; **Conductor**, a multi-agent coding tool built on the Agent SDK, has to publish a retraction (*« Anthropic has delayed the subscription updates to Claude plans »*). **Circle 3 — the underlying tension, which extends beyond Anthropic**: a quote from **Boris Cherny** (head of Claude Code) in April, during an earlier restriction, saying subscriptions *« weren't built for the usage patterns of these third-party tools »* — an acknowledgment that **flat-rate plans and open-ended agentic usage don't mix**; **GitHub** reached the same conclusion, removing Copilot's flat-rate *premium requests* model in June in favor of **token-based billing**, despite the backlash. Added to this, **the same week**, a **proposed class action** was filed in a federal court in California, alleging that **Max** tiers fall well short of the advertised usage multipliers during heavy coding sessions. Anthropic does not say when a revised approach will arrive, only that it *« works to update the plan to better support how users build with Claude subscriptions »*. **The author's final reading**: between government pressure over Fable and Mythos, a planned **IPO**, and **rumored price cuts at OpenAI**, Anthropic is seeking to **keep its developer base on side** — and the suspension is, for now, a way of doing that.
#Anthropic#Claude Agent SDK#Claude subscription
**Paul Sawers** — journaliste tech · signe ici pour **The New Stack**. Registre de **presse spécialisée** : l'article ne relaie pas seulement l'annonce · il la replace dans une série (les changements de facturation successifs d'Anthropic) · la compare à un précédent sectoriel (GitHub Copilot) et l'articule à trois pressions concomitantes (export control, IPO, concurrence). Sourçage explicite et attribué — le billet de Zed · l'analyse de Matthew Diakonov · le post de Conductor · une déclaration antérieure de Boris Cherny.
Blog post on **Zed**'s blog signed by **Franciska Dethlefsen** (head of growth and marketing), published on **May 14, 2026** — the day after Anthropic's announcement — to answer questions from Zed users. **Subject**: starting **June 15**, Anthropic **splits Claude subscription billing into two pools** — one for its **first-party tools** (chat, official Claude Code CLI), the other for **third-party agent and SDK usage** (anything going through **ACP**, `claude -p`, or a third-party tool). Usage via ACP **then stops drawing from Pro or Max limits** and switches to a monthly **"Agent SDK" credit**: **$20 for Pro, $100 for Max 5x, $200 for Max 20x**. Once the credit is exhausted, usage continues **at standard API pricing** if overage is enabled — otherwise requests stop until the next cycle. **The figure driving the article**: subscriptions had until then subsidized agentic usage by a factor of **≈ 15 to 30×** relative to API pricing, and the new credits are billed **at full API pricing** — hence *"for anyone using agents heavily, this is a major cost increase"*. **Three options proposed**, in an order that reveals Zed's position: (1) keep the subscription by launching the **official `claude` CLI in a terminal inside Zed** rather than via ACP — *"when the official claude CLI runs in the terminal, it uses your subscription's limits, not the new credit"*; (2) use Zed's built-in agent with the provider of one's choice (Zed-hosted models, API keys, Copilot, local Ollama, DeepSeek); (3) plug in **any ACP agent** — OpenCode, Codex, Factory, Cursor — several of which still offer rate-limited subscriptions that subsidize heavy usage. **The underlying thesis**, and the real reason for the post: *"ACP is an open protocol… so that your editor is never locked into one provider's pricing decisions"*, with the explicit anticipation that *"this kind of change won't be the last"*. ⚠️ **The post carries an addendum dated June 16, 2026** announcing that **the change is suspended**: ACP, `claude -p`, the Agent SDK, and third-party applications continue to work with subscriptions **as before**, no separate credit to claim, limits unchanged, Anthropic revising its plan with announced advance notice. **The artifact is therefore self-contradicted**: its most important content — the reversal — postdates its own publication date by a month.
#Zed#Anthropic#Claude subscription
**Franciska Dethlefsen** — head of growth and marketing chez **Zed Industries**. Le rôle est déterminant pour lire le texte : ce n'est pas un billet d'ingénierie mais une **communication de crise produit** · écrite le lendemain d'une annonce d'un fournisseur dont Zed dépend · à destination d'utilisateurs inquiets. La signature growth/marketing explique la structure (problème → options → réassurance) et le fait que l'argument protocolaire arrive en conclusion plutôt qu'en tête.