Next.js and the Agentic AI Future: How Vercel is Building a Framework for AI Agents

In an era where AI Agents have become essential tools for developers, Vercel has invested over a year in developing Next.js to work effectively with AI Agents through learning and experimentation

The Problem: AI Agents Can't See the Browser

Earlier this summer, the Next.js team was working on improving devtools when they noticed an interesting pattern. Developers would see an error in the browser, copy the details, and paste them into an AI editor to ask the agent to fix it.

The critical problem was that AI Agents simply cannot see the browser. Runtime errors, client-side warnings, and rendered components are all invisible to them. When a user says "fix the error," the agent doesn't know which error they mean.

lightbulb What the Next.js Team Did First

Their first response was updating the copy button to capture structured error data. Then they added a feature that forwards browser logs to the terminal. These small fixes pointed toward a bigger realization - they needed to make Next.js itself visible to agents

Experimenting with In-Browser Agent: Vector

This understanding led to an ambitious idea. What if they built an agent directly inside Next.js that worked like smart devtools?

The team built an in-browser chat agent called Vector. Similar to react-grab but integrated with Next.js, Vector let you select elements on the page, see their source code, and prompt for changes. It had Next.js best practices baked in to help agents avoid hallucination.

Vector was useful, but it overlapped with general coding agents like Cursor and Claude Code. Most developers were already using those tools for all of their projects anyway, not just Next.js. The UI selection made it easy to point at exactly what you wanted to change, but it wasn't something people needed every day.

The team decided to sunset Vector, but took what made it useful - structured visibility and framework-specific knowledge - and decided to build those directly into Next.js itself.

MCP Made Next.js State Visible to Agents

Around the Next.js v16 release in October 2025, users were struggling to debug with agents. The common prompt was "fix the error," asking agents to resolve issues from the browser overlay. But agents would request the page HTML and find nothing wrong.

Runtime failures, browser JavaScript errors, and async errors all lived in the browser, not in the HTML. The rendered page, layout segments, routes, and other internal state were invisible to agents.

MCP (Model Context Protocol) gave them a way to expose this data. The first version surfaced internal states like errors, routes, and rendered segments, but exposing data alone wasn't enough. Agents also needed to discover running dev servers and communicate with them, which led to next-devtools-mcp.

lightbulb What MCP Can Do

The MCP also packages prompts and tools to help with upgrades and cache component migrations. There's a detailed talk about the MCP integration if you want to learn more

The Answer is to Think Like an Agent

MCP confirmed what Vector taught us. Agents need visibility into what Next.js is doing, but that's only part of the story. The deeper lesson was treating agents as first-class users of Next.js and thinking from their perspective. What information do they need? When do they need it? How do they consume it?

This mindset led to practical changes:

If agents read terminal output during development, logging Server Action invocations and forwarding browser errors gives them the hints they need
If agents struggle with framework concepts not in their training data, embedding a compressed docs index called agents.md or providing structured workflows (Next.js skills) gives them better context than documentation alone

Those questions run through everything they built. The need for visibility led to better logging, the need for knowledge led to agents.md, and the need for discovery led to MCP.

What's Next

The team is now working on making this easier to adopt. You can already run npx @next/codemod to generate an up-to-date docs index for your project, and they're expanding their eval suite to cover more Next.js 16 APIs so they can measure what actually helps agents.

Longer term, they want this built into next dev so agents get the right context automatically without any setup.

When you treat agents as first-class users and meet them where they are, debugging becomes a tight feedback loop between code, runtime, and AI