Cursor Loses Its Largest Supplier Over Its Cap Table
Frontier model access turned out to be revocable on 75 days' notice for reasons no pricing page covers, and the customers of these tools are already substituting providers on their own.
The supplier left during the integration window
SpaceX bought Anysphere, and roughly three months later the asset's largest model supplier gave notice. Techpresso reports OpenAI's stated basis is that it cannot be sure SpaceX will honor its terms of service, citing past contract violations by X and other Musk-owned companies. The explanation says nothing about latency or unpaid invoices. That makes it a governance decision arriving as a supply decision, and governance appears nowhere in the diligence templates used for AI applications.
The useful lesson here is duller than the Musk theatre suggests. An unpriced supplier risk materialized after signing, inside the window where an acquirer has the least room to respond. This is probably an overcorrection, but applications running on a rival lab's models now deserve diligence with change-of-control severance as the base case.
Both counterparties can leave cheaply
The demand side does the same thing from the other direction. A legitimate device-reclamation task tripped Claude's safeguards and the user worked through Kimi K3, GLM-5.2 and GLM-5.3 until one produced a working path, part of a $266 spend across four models over five months. Refusal didn't slow him down, it moved him to three other vendors in the same session.
Single-supplier AI applications hold a permission slip with a 75-day notice period.
So the application layer sits between a supplier that can cut access on 75 days' notice and a customer who substitutes in an afternoon. After November 12, Cursor runs on Anthropic plus an unproven in-house Composer model. Anthropic most likely serves and reprices, though it could decline outright as OpenAI did, and either way it gains pricing leverage over the AI coding cohort while it inherits the identical decision OpenAI made about serving a Musk-owned entity. Higher COGS for every portfolio company in the cohort.
The moat question underneath
Techpresso also surfaces research showing hidden agent skills reconstructed at roughly 87% fidelity in about 32 requests against a paid specialized service, with disclosure protections enabled. A vertical agent defended by proprietary prompts is a software multiple paid for a feature with a 32-request replication cost. The counter-thesis is that distribution and enterprise trust were always the moat, and The Information Weekend's account of the multi-agent incident supports it: procurement now asks agentic vendors for audit rights, immutable action logs and containment boundaries. "We monitor it internally" no longer clears the gate.
Where the reads diverge
Techpresso puts value capture in multi-model routers and gateways, now a board-level line item rather than architecture hygiene. Exponential View locates it one layer down, in fine-tuning and distillation platforms that intermediate enterprises away from frontier APIs entirely. Both are bets on owning the substitution path; the disagreement is only about which layer the buyer will pay for. Sourcing, not conviction, binds next quarter, and hours spent on router plumbing are hours not spent on the product that was supposed to be the moat. Every CTO in the cohort has budget for this and few vendors to spend it with.
What to do
Run a 72-hour model-dependency audit across every AI application position: named provider, share of inference by workload, termination-for-convenience and change-of-control clauses, notice period, and measured time-to-swap in days.
Add a supplier-continuity section to the AI diligence template before the next investment committee, covering multi-provider architecture, ownership-change triggers, and a documented open-weight fallback.
Commission an independent replication estimate on every vertical-agent deal in pipeline this quarter, tested against the 32-request extraction result before any partner meeting.