Nuxt v4.6.0 is the next minor release, and it lands alongside a new major version of the CLI: @nuxt/cli v4. Because the CLI ships as a dependency of nuxt, upgrading the framework brings it in automatically — no separate install step required.
Most of the new work lives in nuxt dev:
- An interactive terminal UI showing URLs, startup progress and keyboard shortcuts, with panels for error logs, routes, network requests and more.
- A more informative dev server: it explains why it reloaded or restarted, which
nuxt.configkeys changed, where time went during a slow start or build, and how long each module took to set up. - A CLI-level error channel rendered with
my-bad, powering behaviour such as automatically reloading when a syntax error innuxt.config.tsis fixed. - A lock file in
.nuxt/, letting a secondnuxt dev(for example, one started by an agent) take over or defer to the one you started. - New
nuxt curlandnuxt taskcommands that talk to the running server, plus a newnuxt docssearch. nuxt preview --takeover, which can replace a running preview server.
Overall, nuxt/cli is substantially smaller and starts much faster: version v3.37 to v4.0.
For developers, this release turns the dev server from a black box into an observable tool. The terminal UI and richer startup diagnostics cut the time spent guessing why a reload happened or a build stalled, while the .nuxt/ lock file and takeover commands make parallel sessions — including agent-driven ones — practical. Faster CLI startup also compounds across every nuxt dev invocation in a working day.