v0 Adds /changelog page Alongside Faster Previews and Integration Fixes.

v0 has launched a dedicated changelog and shipped a cluster of improvements aimed at making AI-generated applications more reliable. The release combines faster Design Mode previews, stronger Postgres integration code, and fixes for several issues that could interrupt editing or prevent previews from loading.

The company announced the update on LinkedIn, pointing users to the new /changelog page for regular release notes. While the page itself is the most visible addition, the practical value of this release lies in smaller changes across generation, previewing, and integrations.

The /changelog page gives users a central place to track new features, interface changes, and bug fixes. That matters for a product evolving as quickly as v0, where changes to models, integrations, and generated code can alter how an existing workflow behaves.

A structured changelog should also make it easier for teams to diagnose changes without relying on social posts. Builders can check whether an unexpected behavior is a known issue, see when a fix shipped, or review recent releases before adjusting production workflows.

This follows a broader push to make v0 more usable in professional and automated environments. The company has previously added a Usage & Activity Dashboard for granular AI cost tracking and opened the v0 API to agents and automated workflows. A public release history adds another layer of operational visibility.

v0 says it optimized preview loading performance when Design Mode is active. Design Mode allows builders to work visually with an application, so preview latency can directly affect how quickly they can inspect and iterate on generated interfaces. The announcement did not provide benchmark figures, meaning the scale of the improvement will depend on the project and environment.

The release also fixes a potentially costly editing bug. Pending changes could previously disappear when a user switched between the Code and Preview panels. Preserving those edits reduces the risk of losing unfinished work while moving between implementation and visual inspection.

Other preview and connection fixes include:

• Resolving cases where certain npm modules failed to load inside the preview.
• Preventing an AI Gateway connection dialog from appearing when the gateway was already connected.
• Refining the interface styling for Model Context Protocol, or MCP, features.
• Updating Linear’s logo in the product.

The npm correction is particularly relevant for generated apps that depend on third-party packages. If a module cannot load in the preview, a working implementation may appear broken before deployment, making it harder for nontechnical users to distinguish an environment problem from faulty generated code.

Database generation also received attention. v0 says it is now better at writing code for Postgres integrations. No specific queries, libraries, or supported providers were identified, but more reliable database code could reduce the manual repair work required when generated apps need persistent data, authentication records, or application state.

One framework-specific safeguard targets Next.js 16. When v0 generates a middleware.ts file that requires correction, the product can now apply an autofix. Middleware often sits in sensitive request paths such as authentication, redirects, and access control, so invalid or outdated code can stop an otherwise functional application from running correctly.

Taken together, the update is less about a single headline capability than reducing friction across the build loop. For small businesses using v0 to move from a prompt to a functioning web application, faster feedback and fewer silent failures may prove more useful than another generation feature.

What is v0 /changelog page?

The v0 /changelog page is a public release log for new features, product changes, and bug fixes. It gives users a permanent location to follow updates instead of depending only on announcements posted through social channels.

What changed in v0 Design Mode?

v0 optimized preview loading performance while Design Mode is in use. It also fixed a bug that could discard pending edits when switching between the Code and Preview panels, although the company did not publish performance benchmarks.

Does the update require a particular v0 plan?

The announcement did not specify plan restrictions or additional pricing for the /changelog page, preview optimizations, Postgres improvements, or listed bug fixes. Users should consult v0’s current product and plan documentation if access differs by account.