Bring Back Editable Code — AI Shouldn’t Be the Only Way to Code - v0

With the recent v0 update, the code editing experience has changed significantly. According to the latest Code Editing documentation (https://v0.app/docs/code-editing), the Code view is now primarily for viewing code, while code changes are expected to be made through the conversation.

v0.app

Code editing | v0 Docs

Edit v0's code output directly in the browser.

I understand and appreciate the direction toward AI-assisted development, but I strongly believe that manual code editing should remain available.

Not every code change needs AI. For small, precise changes—such as adjusting a CSS value, changing a string, fixing a typo, or making a minor logic change—users should be able to edit the code directly without consuming AI credits.

Requiring a conversation for every code change has several drawbacks:

Small changes unnecessarily consume credits.
AI-generated changes may modify more code than intended.
The final result is not always exactly what the user requested.
Developers lose direct control over the source code.
Simple one-line fixes become unnecessarily slow and inefficient.

For example, if I already know that I need to change padding: 16px to padding: 12px, there is no reason to spend AI credits asking an agent to make that change for me. Direct editing is faster, more precise, and gives the developer full control over the result.

AI should make coding faster, not become the only way to modify code.

A better workflow would be to support both:

AI for generating, refactoring, and complex changes + direct code editing for small, precise changes.

The ability to directly edit source code is especially important for developers who use v0 for real projects rather than just prototypes. Please consider bringing back an editable Code Editor, even if it is positioned as an advanced/developer mode.

If manual code editing is permanently removed, I may unfortunately have to reconsider my subscription and evaluate migrating my projects to another platform that provides both AI-assisted development and direct code editing.

AI + Code Editing, not AI instead of Code Editing.

If I need to make a tiny change like:

max height: max-h-[calc(100vh-7rem)] → max-h-[calc(100vh-10rem)]

I can make that change myself in a few seconds.

Instead, I now have to spend time explaining the change to AI, wait for it to process the request, consume credits, and then verify whether it actually made the change I wanted.

By the time I finish typing the prompt, I could have already fixed the code myself.

This is not making development faster. It is adding an unnecessary layer between the developer and their own source code.

Just changed one value, which cost me 0.653 credits.
Before this update, I was able to manually update this value. Who exactly decided to disable this editing feature? Did anyone ask our actual users?

To the & team: Disabling manual code editing in the latest update is a massive step backwards.

Turning the code editor into a read-only viewer and forcing users to prompt the AI for a single CSS tweak, typo fix, or one-line logic change is completely counterproductive. It wastes user credits, burns time waiting on generations, and risks the AI hallucinating or modifying unrelated code.

We subscribe to the v0 Plus plan to build faster, not to lose control over our own files. AI should assist developers, not lock us out of our code.

If direct inline code editing isn't restored immediately, there is zero reason for paying developers to stay when tools like Cursor, Bolt, and Lovable respect our workflow. Bring back the code editor.

Screenshot 2026-09-24 213602.png