DJTL
<- articles
May 19, 20264 min read

One for all or all for one?

Most developers drifted into depending on one AI platform without making an active choice. Three recent incidents show what that costs when something changes.

Thomas Indrias

TL;DR: Most developers drifted into depending on one AI platform without making an active choice. Three recent incidents show what that costs when something changes. Model quality at the top has converged. Pricing has not. Worth thinking about before you have to.

Here is a fun little thing that happened to us.

We looked at our setup one day and realized Claude was running basically everything. Not because we planned it that way. Not because we sat down and said "yes, one vendor, let's go." It just... accumulated. CLAUDE.md in every project, prompts tuned to one model, muscle memory doing the rest. The stack had opinions and we had stopped having them.

Creative people building on autopilot. Not our best look.

The industry has had a rough few months that make this worth talking about.

Anthropic restricted Opus access through tools like OpenCode earlier this year. Developers had no fallback. Not because building one is hard. Because nobody had thought about it.

Cursor quietly halved effective monthly requests. Same $20. No warning. The CEO apologized. People left.

Lovable, $6.6 billion valuation, teams at Nvidia and Microsoft building on it, exposed source code and database credentials for 48 days. Bug reports filed. Bug reports closed. When it came out their first response was that the exposure was intentional behavior.

Reader, it was not intentional behavior.

Every credential that had touched the platform had to be rotated and assumed compromised.

These are not uniquely bad companies. They are fast-moving ones. And fast-moving platforms make fast-moving decisions that your workflow did not account for.

We use Claude daily, Codex for heavier agentic work (agents.md pulling the same weight as CLAUDE.md on the Anthropic side), Gemini when the task calls for it. OpenCode as the connective tissue since it talks to 75+ providers and lets you swap models mid-session without losing your thread. Messy to set up once. Extremely not messy when something changes.

The whole point of creative thinking is that you stay in the driver's seat. That goes for AI tooling too.

What does your stack look like right now? And be honest, was it a choice or did it just happen to you?