Long-form article published on **X** on **August 11, 2026** by **Jesse Zhang**, CEO of **Decagon** (customer-service AI agents), under a dilemma-shaped title — *« To FDE, or not to FDE? »* — devoted to the **Forward Deployed Engineer**, which has become *« the answer to almost every hard question in AI go-to-market »*. Starting observation: Anthropic and OpenAI have built enterprise deployment arms explicitly modeled on Palantir, *« every seed-stage company »* advertises an FDE offering, and job postings for the title are said to be up several hundred percent in a year. **(A) The Palantir genealogy** supplies the framework: **Shyam Sankar**'s (CTO) formula, *« FDEs eat pain and excrete product »*, and **Joe Lonsdale**'s reminder that Palantir spent nearly two decades being called a *« glorified consultancy »* on the basis of an accurate observation. **Gotham**'s bespoke deployments (CIA, NSA, military intelligence) were encoded into platform primitives — ontology, object models, permissions, workflow engines, provenance tracing — which became **Foundry**, then Apollo and AIP; standardization pushed gross margin into the 80% range and Palantir moved from an FDE motion to account-based selling, with many FDEs migrating into core engineering. *« The pain was the input to the product, not a cost of sale. »* **(B) The criterion proposed** is not to give up on FDEs but to know when to stop: go early, then ask whether one is still **discovering** — *« The trap is not starting. It's not stopping. »* **(C) A distinction few make: FDE ≠ implementation.** *« Building that integration into their ticketing system »* is real work, but it is execution against a known spec, not discovery of an unknown one; conflating the two *« is how a company convinces itself that a growing services org is a product investment »*. Closing line: *« If your FDEs are eating pain and excreting more pain, you don't have an FDE team. You have a services business. »* Two figures are put forward about Decagon — *« two-thirds of deployment work is now done autonomously via Duet »* and *« a few days on average to launch the first AOP, even for large banks, airlines, telcos »* — without the "deployment work" denominator being defined or the AOP acronym spelled out.
#Forward Deployed Engineer#FDE#engineer embedded with the client
**Jesse Zhang** — cofondateur et **CEO de Decagon** (agents IA de service client, San Francisco) · 85 000 abonnés sur X · site personnel `jessezhang.org`. Il cite son cofondateur **Ashwin Sreenivas** · **ex-Palantir** · d'où la profondeur du récit Palantir. Publié le **11 août 2026**.
**Zed** blog post signed by **Franciska Dethlefsen** (head of growth and marketing), published on **May 14, 2026** — the day after Anthropic's announcement — to answer Zed users' questions. **Subject**: starting **June 15**, Anthropic **splits Claude subscription billing into two pools** — one for its **first-party tools** (chat, the 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 the 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 rates** — hence *« for anyone using agents heavily, this is a major cost increase »*. **Three options are proposed**, in an order that reveals Zed's position: (1) keep the subscription by running 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 advance notice announced. **The artifact is thus self-contradicting**: 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.