@haram
Have you seen the recent Next.js 16.3 preview announcement? This update clearly highlights the direction of becoming a 'web framework for AI agents.' Many new features have been added, which are particularly useful for those using tools like Cursor or Claude Code.
The most interesting part is that they have started officially using the AGENTS.md specification. When you create a project with create-next-app, this file is generated automatically. When the dev server is started and an AI agent is detected, it prompts the agent to first read the correct version of the framework documentation stored locally in the node_modules/next/dist/docs/ directory. According to internal Vercel evaluations, giving the agent direct access to local docs instead of having it call search tools significantly reduces errors, resulting in a 100% success rate. 😄
The next-devtools-mcp feature, which allows you to connect the dev server environment entirely to an agent, is also very attractive. You can have the agent read error logs and look up the routing map to debug issues on its own. Setting it up is much easier than you'd think. Simply copy the following configuration into your local or global .mcp.json file and you're good to go.
{
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": ["-y", "next-devtools-mcp@latest"]
}
}
}In addition, the existing next-browser CLI has been integrated into the agent-browser library, allowing agents to utilize headless Chrome and the React DevTools directly. To find the source of an error, you can run npx skills add vercel-labs/next-browser in your terminal and have the agent inspect the React component tree. Since you no longer need to tediously paste code into the agent manually, the development experience is going to be incredibly smooth~ 😄