概要
公開日: 2026-06-26
翻訳生成に失敗したため、原文をそのまま保存しています。
原文
Back to Blog Friday, June 26th 2026 Next.js 16.3: AI Improvements Posted by Aurora Scharff @ aurorascharff Jude Gao @ gao_jude Next.js 16.3 Preview is ready for public testing! We've published a new Next.js release to npm using the @preview tag, so you can try out 16.3 starting today. We expect to ship a polished stable release in the coming weeks. We'd love to hear any feedback you have about the preview on GitHub . As the Next.js 16.3 Preview nears a stable release, we're sharing a series of posts about what's inside. The first post, Instant Navigations , covers the new rendering and prefetching primitives. This second post focuses on AI improvements. Next.js has grown a lot since the App Router went stable, and more and more of that growth is driven by code written through agents like Claude Code, Cursor, and Codex. What would Next.js look like if it were designed primarily for agent-driven development? We're not all the way there yet, but we're getting closer with every release. Next.js 16 added the DevTools MCP server, and Next.js 16.2 brought bundled docs and next-browser , an experimental CLI for letting agents drive a real browser. In Next.js 16.3, we're extending this with: Bundled docs through AGENTS.md : Keeps agents reading version-matched docs instead of their training data First-party Skills : Skills that help agents drive multi-step workflows Agent Browser with React introspection : Drive a real browser and inspect React state from agent-browser Actionable errors : Copy the fix you picked from the dev overlay as a paste-ready prompt, mirrored in the terminal and per-rule docs pages A smaller, more focused MCP server : New tools for build diagnostics, with the knowledge-base ones retired Docs as Markdown : Append .md to any docs URL for a plain Markdown version Bundled docs through AGENTS.md In our previous 16.2 release, we started bundling the Next.js documentation into your project so agents can read it locally. Projects created with create-next-app on 16.2 or later already point AGENTS.md to those docs. In 16.3, next dev writes and updates that pointer automatically, so existing projects stay current as you upgrade. On 16.1 or earlier, run the agents-md codemod manually: terminal npx @next/codemod@canary agents-md Here's what next dev inserts into your AGENTS.md : AGENTS.md <!-- BEGIN:nextjs-agent-rules --> # This is NOT the Next.js you know This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices. <!-- END:nextjs-agent-rules --> The block is only written when next dev detects an AI coding agent in the environment and the markers aren't already there. Anything outside the markers is preserved, and you can opt out with agentRules: false in next.config.ts . Commit the block as-is, even if it shows up as an uncommitted change. First-party Skills Skills give agents framework-specific context. You may have installed our earlier knowledge Skills from skills.sh , which covered App Router conventions and caching APIs. With the bundled docs now reaching agents through the managed AGENTS.md block , we're retiring those Skills. Run npx skills update to remove them from your installed set. Skills are still useful for multi-step workflows that docs alone can't drive end to end. Next.js 16.3 adds three new first-party Skills for those. next-dev-loop The next-dev-loop Skill gives your coding agent access to the full development feedback loop. It can drive the browser, read the console, follow network requests, and inspect the React tree as it iterates. /_next/mcp , the framework's view of routes, server logs, and compilation issues. agent-browser , the browser's view of the DOM, console, network, and React tree. The Skill requires agent-browser version 0.27 or later. terminal npx skills