About this formation"Developer Tools" as a category label is cooling by the numbers, growing at just 0.48× while every formation statistically tied to it, Infrastructure at 1.48×, Cloud Computing at 3.10×, LLM Application at 4.68×, AI Agent Infrastructure at 4.71×, is accelerating hard, and the roster here explains why: almost nothing in this batch is a tool for writing code anymore, it's a tool for supervising code that agents already wrote. Compyle asks permission before acting, Lemma and The Context Company hunt for the moment an agent looked successful but wasn't, IncidentFox and Kestrel try to catch or fix what an autonomous system broke, and Coasts exists purely because agents now run in parallel across git worktrees and need isolated machines to do it safely. That's a real shift in what the category used to mean: the old developer-tools pitch was "help a person code faster," the new one is "govern a fleet of agents that code without you," and Sourcebot's push into understanding massive codebases for companies like NVIDIA and Wikimedia fits the same governance logic rather than the old autocomplete logic. The live interest in machine-readable lineage from request through generated code to rollback confirms this: once an agent can produce a large, unreviewed diff, the bottleneck stops being generation speed and becomes trust and reversibility. This reframing only became urgent once agentic coding tools capable of multi-file, autonomous changes went mainstream through 2024 and 2025, which is exactly when the older, simpler "developer tools" label started splitting off into the faster-growing agent-infrastructure and observability formations around it.
Cambrian Signal, “Developer Tools,” publication yc-2026-10-02-semantic-v8, snapshot October 2, 2026.
cambrian.jafar.com/formation/developer-tools