Vercel says coding agents now trigger over half of all deployments

At Vercel Ship 26 in London today, Guillermo Rauch launched what he's calling the Agent Stack: AI SDK, AI Gateway, Sandbox, Workflow SDK, and Chat SDK, plus a new Vercel Connect and a set of enterprise agent controls. Vercel is repositioning the entire platform around running agents in production. That's a big swing for a company most people still think of as "the Next.js deploy button."

The metric that stopped me: coding-agent-triggered deployments went from under 3% to over 50% in six months. And AI Gateway token volume grew from roughly 2 trillion to 20 trillion per month. Ten times, in half a year. Even if you discount the framing, the direction is unmistakable. Deploy is becoming a machine action.

Think about what that does to your assumptions. CI gates, deploy approvals, rollback procedures, observability dashboards. Most of that tooling assumes a human pushed the button and a human is watching. When the agent pushes 50% of the time, your release process is now an agent-to-infrastructure interface, and the human is reviewing after the fact or not at all. That's a different design problem.

I'm a little skeptical of the headline number because Vercel has every incentive to count generously. A deployment "triggered by" a coding agent could mean an agent ran git push on a branch a human is babysitting. But the token-volume growth is harder to spin. 20 trillion tokens a month flowing through one gateway is real consumption, and it maps to the loop-engineering story above. If your loop deploys, it deploys through something, and increasingly that something is purpose-built.

For builders, the move is to invest in protocol-portable config rather than betting your workflow on one vendor's agent surface. Vercel's stack is convenient if you're already there, but the smart hedge is keeping your deploy logic in standard, exportable form. The same week, The New Stack argued that Cursor, Claude Code, and Codex are quietly merging into one interoperable stack via ACP and MCP. The platforms are converging on protocols faster than they're locking you in. Design against the protocol, not the product.