Next.js 16.3.0 is shaping up to be one of the most interesting releases in a while. Vercel is betting hard on AI-assisted development. And they're fixing the edge cases that make caching a nightmare.
Hi, my name is Tom Smykowski, I'm a staff full-stack engineer. I build and scale SaaS platforms to millions of users, working end-to-end from system architecture to frontend to mobile. On this blog I write about modern web development, AI-assisted coding, and production engineering challenges.
The canary releases tell a clear story: Next.js is becoming AI-native. Not in the "we added a chatbot" sense, but in the "AI agents can now compile your routes without spinning up a server" sense.
Let me walk you through the three features that matter most: MCP compile_route for AI agents, deadlock detection for 'use cache', and bfcacheId for controlling browser navigation state.
These aren't flashy features for conference demos. They're the kind of improvements that make you say "finally" when you read the changelog.