Next.js 16.2 is the first framework release designed primarily around how AI agents interact with a codebase. The headline feature: create-next-app now includes an AGENTS.md file by default, giving coding agents access to version-matched Next.js documentation from the moment a project is scaffolded.
The approach is backed by Vercel's own evaluation data. Bundled documentation achieved a 100% pass rate on Next.js evals, compared to 79% for skill-based retrieval. The core insight: always-available context outperforms on-demand search because agents frequently fail to recognize when they should look up documentation.
Browser Log Forwarding
Next.js now forwards browser errors to the terminal by default during development. This is a practical fix for a real problem — AI agents operate through the terminal and can't access a browser console. With logging.browserToTerminal in next.config.ts, you can control the level from errors-only (default) to full console output.
Dev Server Lock File
A new .next/dev/lock file stores the running dev server's PID, port, and URL. When a second next dev tries to start, it gets an actionable error with the PID to kill or URL to connect to. This directly addresses a common agent failure mode: blindly starting a dev server without knowing one is already running.
Experimental Agent DevTools
The most ambitious addition is @vercel/next-browser, an experimental CLI that exposes browser-level data — screenshots, network requests, console logs — along with React DevTools output as structured text. Agents can inspect component trees, analyze PPR static shells, monitor network activity, and capture screenshots, all from shell commands against a persistent browser session.
This release marks a shift in how frameworks think about their audience. The developer is still the primary user, but the agent is now a first-class consumer of framework APIs, error messages, and documentation. Every framework that doesn't adapt to this will lose agent compatibility by default.