The Next.js team shares how they spent the past year improving AI agent support in the framework. They built and sunset an in-browser agent called Vector, then shipped MCP integration via next-devtools-mcp to expose runtime state like errors, routes, and rendered segments to agents. The core lesson: treat agents as first-class users by giving them visibility into framework internals, embedded docs (agents.md), structured workflows (Next.js skills), and better logging. Future plans include baking this context automatically into next dev.
Table of contents
Agents couldn't see the browserExperimenting with an in-browser agentMCP made Next.js state visible to agentsThe answer is to think like an agentWhat's nextSort: