Next.js

React framework for server-centric apps on Vercel and elsewhere. For agents, Next.js 16.3 moves framework knowledge into version-matched local docs and keeps skills for multi-step workflows.

Current Source Snapshot

As of the 2026-08-12 refresh, npm next@latest is 16.3.0, the maintained 15.x backport is 15.5.23, and next@canary is 16.3.1-canary.12. The pinned GitHub source snapshot is vercel/next.js@ae1e53a11f5379e715096b829178f4df92d35044. agent-browser@latest is 0.34.0; the machine's global 0.32.3 remains usable but should not be reported as current. Next.js 16.3's agent-facing documentation, managed AGENTS.md pointers, workflow skills, error output, and browser introspection are stable release behavior now. Instant Navigation still needs project-specific production proof rather than a framework-version assumption. Source: npm registry and GitHub vercel/next.js, 2026-08-12

Agent Routing

When a task touches a Next.js app:

1. Read the app's own AGENTS.md, then the installed Next docs pointer in node_modules/next/dist/docs/ or node_modules/next/docs/llms.txt if present.
2. Load next-best-practices for App Router, RSC, metadata, bundling, runtime, and navigation rules.
3. Load next-cache-components or the official next-cache-components-* workflow skills only when the task touches Cache Components, use cache, route shells, or instant navigation.
4. Use next-dev-loop or equivalent browser verification for runtime-sensitive UI changes; compile-only checks are not enough for App Router work.
5. Recheck the installed Next version, feature flags, and bundled docs before applying 16.3 behavior. Stable availability does not prove that Cache Components, Partial Prefetching, or Instant Navigation fit the target route. Source: Next.js 16.3 AI Improvements, 2026-06-26

Next.js 16.3

The June preview has become the stable 16.3 line. Upgrade through the project's normal dependency, advisory, migration, and regression path; do not turn the old preview announcement into permission to enable every new rendering option. Source: Next.js 16.3 Instant Navigations, 2026-06-25; npm registry, 2026-08-12]

Instant Navigations

Instant Navigations are the 16.3 attempt to make server-driven App Router navigation feel SPA-like. The route must either:

• Stream with <Suspense> so a useful loading shell appears immediately.
• Cache with 'use cache' so previously generated UI is instantly reusable.
• Block intentionally with export const instant = false when the product should wait for the server response.

The main flags are:

import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  cacheComponents: true,
  partialPrefetching: true,
};

export default nextConfig;

With Partial Prefetching, Next.js prefetches a reusable shell per distinct route rather than one request per link. <Link prefetch={true}> opts a specific link into deeper prefetching, bounded by what is synchronous or cached. Source: Next.js 16.3 Instant Navigations, 2026-06-25

Verification shifts from "the route eventually loaded" to "the shell is useful immediately." Use the instant() Playwright helper from @next/playwright for regressions, and use Navigation Inspector to inspect the prefetched shell. Known preview issues include some missed blocking-route reports and Safari Instant Insights tooling problems; develop with Chrome or Firefox for best results. Source: Next.js 16.3 Instant Navigations, 2026-06-25

The Liveblocks Linear-like issue tracker demo is a good test case because the user can feel the before/after navigation delta on a realistic collaborative app surface, not a contrived blank route. Use examples like this to judge perceived shell quality: the route should expose useful issue-list or detail context immediately while dynamic data resolves. Source: X/@ctnicholasdev, 2026-06-26

Counter-signal: Tejas Kumar's critique is useful because his self-reply narrows the complaint to a specific architecture, not generic Next dislike. He wanted a static shell with client-fetched per-user hydrated islands, followed the docs on a large user-facing app, and still found every performance win expensive enough that he moved the build to Astro. Treat this as a framework-fit warning: if a route is mostly static chrome plus personalized client islands, validate Next's PPR/Cache Components path with real traces before adding more framework machinery. Source: X/@TejasKumar_ self-reply, 2026-06-27

AI Improvements

Next.js 16.3 makes agent work more explicit:

• next dev can insert and update a managed AGENTS.md block that points agents to version-matched local docs.
• Older knowledge skills from vercel-labs/next-skills are being retired because bundled docs now own framework reference.
• Workflow skills remain useful where docs alone cannot execute the loop: next-dev-loop, next-cache-components-adoption, and next-cache-components-optimizer.
• agent-browser 0.27 introduced React DevTools introspection for DOM, console, network, Web Vitals, component tree, render profiling, and Suspense inspection; latest checked package is 0.34.0.
• Instant Insights expose Stream/Cache/Block fixes with "Copy as prompt" output, structured terminal output, and per-rule docs pages under nextjs.org/docs/messages.
• DevTools MCP is smaller: knowledge-base tools are removed, while get_compilation_issues and compile_route give fast build diagnostics from the running dev server.
• Docs pages can be fetched as Markdown with .md; indexes live at /docs/llms.txt and /docs/llms-full.txt.

The important routing shift: framework facts belong in local versioned docs; skills belong to workflows. Source: Next.js 16.3 AI Improvements, 2026-06-26

Security Patch Line

The 2026-05-07 bookmark is a security signal, not a timeless minimum version. Next.js shipped v16.2.6 and v15.5.18 with fixes for multiple high, moderate, and low severity advisories, including Server Components denial of service, middleware/proxy bypass variants, WebSocket upgrade SSRF, XSS, image optimization denial of service, RSC cache poisoning, and redirect cache poisoning. Later advisories raised maintained-line fixes to at least 16.2.11 and 15.5.21, and the current registry has moved again. Resolve the installed line and feature exposure against current maintainer advisories, then upgrade to the newest applicable maintained patch and test affected routes. Source: X/@nextjs, 2026-05-07; Next.js releases and advisories, checked 2026-08-12]

Relationship To View Transitions

React View Transitions remains the route for React's declarative <ViewTransition> component and motion polish. Next.js 16.3 Instant Navigations are a broader rendering/prefetching system: route shells, Cache Components, Partial Prefetching, Instant Insights, and regression tests. Use both only when the route needs fast state plus motion polish. Do not conflate the current 16.3 Preview with older ViewTransition-only examples.

---

Timeline

• 2026-08-12 | Refreshed the framework state after the saved 16.3-preview signals: next@latest is now 16.3.0, next@canary is 16.3.1-canary.12, the 15.x backport is 15.5.23, and agent-browser@latest is 0.34.0. Promoted docs-first agent behavior to the stable route while keeping Cache Components, Instant Navigation, and Turbopack performance behind target-app regression and production measurement. Source: npm registry; vercel/next.js@ae1e53a, 2026-08-12
• 2026-07-03 | Deep-reviewed the actionable-errors artifact: the overlay exposes Stream, Cache, and Block fix cards with Copy-as-prompt controls, matching the official 16.3 AI Improvements post. Refreshed canary to 16.3.0-canary.76; next@latest, next@preview, and agent-browser@0.31.1 stayed unchanged. Source: X/@rauchg, 2026-06-25; Next.js blog; npm/GitHub, 2026-07-03
• 2026-07-04 | Added Tejas Kumar's self-reply as a framework-fit counter-signal: static shell + client-fetched personalized islands may be cheaper in Astro/islands architecture than in a Next app where PPR/RSC/use cache complexity fights the target shape. Source: X/@TejasKumar_, 2026-06-27
• 2026-07-01 | Refreshed npm registry snapshot: next@latest 16.2.10, next@preview 16.3.0-preview.5, next@canary 16.3.0-canary.73; agent-browser remains 0.31.1. Source: npm registry packument, 2026-07-01
• 2026-06-30 | Deep-reviewed the root Next.js 16.3 AI Improvements thread (2070556819978866969) plus all five self-thread items. Refreshed vercel/next.js HEAD, npm dist-tags, and agent-browser@0.31.1; decision remains docs-first plus workflow skills, not a stable-project default upgrade. Source: X bookmark artifact audit, 2026-06-30; Next.js blog; npm registry; GitHub vercel/next.js
• 2026-06-26 | Next.js 16.3 AI Improvements published: managed AGENTS.md, retired knowledge skills, new workflow skills, agent-browser React introspection, actionable errors, focused MCP, and Markdown docs. Source: Next.js blog, 2026-06-26
• 2026-06-25 | Next.js 16.3 Instant Navigations preview published: Cache Components, Stream/Cache/Block choices, Partial Prefetching, instant() Playwright helper, Navigation Inspector, and next@preview. Source: Next.js blog, 2026-06-25
• 2026-06-30 | Deep-reviewed the May security bookmark and the Next 16.3 AI bookmark; recorded current npm dist-tags, canary HEAD, the security-release advisory categories, and the routing decision that stable projects should not silently adopt 16.3 preview behavior. Source: X bookmark artifact audit, 2026-06-30
• 2026-06-30 | Deep-reviewed the Liveblocks issue-tracker demo as a realistic perceived-speed example for Instant Navigations shell quality. Source: X bookmark artifact audit, 2026-06-30