|
The Brief
Your Toolchain Is Someone Else's Moat Now
By Sergey Zelensky · 2 min read · OPINION
Two beloved open-source projects, zero combined revenue, both acquired by AI companies within four months. Bun went to Anthropic in December. Astral - the team behind uv and ruff, downloaded 126 million times last month - went to OpenAI this week. The pattern is obvious. What it means for where your lock-in actually lives is less so.
The surface story is simple: AI coding agents depend on developer tooling, and both companies decided to own their dependencies rather than pray the maintainers stick around. Claude Code ships as a Bun executable. Codex needs Python tooling to work. Fine. But the real action is one layer up, where Anthropic and OpenAI are running opposite platform strategies that will shape which walls your team builds inside this year.
Anthropic went vertical. They locked OAuth tokens to first-party tools only, breaking every developer using OpenCode, Cline, or Roo Code overnight. The economics are honest - a $200/month Max subscription bleeds money when users route agentic workloads through third-party tools that strip out rate limits. Control the interface, control the margin. OpenAI took the opposite tack, and the irony is thick. The company that went from "open" to closed with GPT-4 is now the ecosystem champion. They open-sourced the Codex CLI, let subscriptions work in third-party tools, and when Anthropic locked developers out, extended support to those same tools within hours. Game theory textbook stuff.
| |
The MIT license on uv protects your right to fork. It doesn't protect your roadmap from serving someone else's product.
|
|
But both paths converge. OpenAI's acquisition spree - Astral, Promptfoo, Crixet - is quietly assembling the full developer lifecycle under one roof. The MIT license on uv protects your right to fork. It doesn't protect your roadmap from serving someone else's product. Features that serve Codex rise to the top. Everything else drifts. That's not platform lock-in. It's infrastructure lock-in, at a layer below the application.
The part I can't fully resolve: does it matter? Both projects were VC-funded with no path to revenue. The realistic alternative wasn't independence forever - it was a painful monetization pivot or slow decay. Bun's team said it plainly: joining Anthropic meant skipping the chapter where they figure out monetization. Getting acquired by a company with a billion-dollar coding product that depends on your tool might genuinely be the best outcome available. But that makes the next independent dev tools startup harder to fund, not easier.
Audit which AI coding tools your team has standardized on this quarter. Then look one layer deeper at which infrastructure those tools quietly pulled into your workflow. The model choice is the decision you see. The toolchain dependency is the one that'll be harder to unwind.
|
