Next.js 16.4 makes Cache Components default, adds upgrade command for agents

Running create-next-app on a fresh machine now produces a different project than it did a day earlier. The caching model that was behind a flag for a year is the default output.

Next.js released 16.4 on 7 October 2026, with Cache Components turned on for every new project and marked as the recommended choice for every existing one. The post, written by nine or more members of the Next.js team, says Cache Components will be the default in Next.js 17. The release also adds next upgrade --agent and dedicated Skills so a coding agent can perform the migration, and bundles React 19.3 along with cuts to memory use, disk size and compile time.

What Cache Components change

Cache Components is a 'use cache' directive paired with cacheLife that acts like a Cache-Control header on a React component. A Projects component inside a dashboard page marks itself cacheable for 'hours', and Next.js caches its rendered output in the browser during client navigations and, optionally, on the server during server rendering or at build time. Mixing a cached blog post with a request-time <UserAvatar /> on the same page produces one HTTP response that streams both.

Next.js 16.4 turns on the model in next.config.ts with cacheComponents: true and partialPrefetching: true, both now considered part of the same programming model.

The new static guarantee

The release adds ensureStatic, a route-level export that forces a shell, a prefetch or a full navigation to stay static. Writing export const ensureStatic = 'navigation' on a route turns a dynamic component slipped in later into a build-time error instead of a request-time cost. The point is to stop a route that was supposed to be free from quietly starting to run on every visit, which is a common source of unplanned server bills.

The migration runs through an agent command

The post that announces 16.4 also makes clear that the migration path is a coding agent, not a codemod. next upgrade --agent writes version-specific guidance the agent reads before touching the project, and dedicated Skills, in the sense Anthropic uses the word, cover the rewrites from unstable_cache and other caching APIs to use cache. The team put the agent tooling in the headline of the release post.

For a reader who held off on Cache Components during the beta, the release answers two questions. New apps now adopt the new model by default, so the direction is set. Existing apps have Next.js 17 as the deadline, and the way the team expects the rewrite to happen involves a coding agent reading documentation the framework handed it.

Source

Next.js 16.4 and the v16.4.0 release on GitHub.