New Design Mode: Why do simple edits now require AI credits?

v0
1

In the previous Design Mode, I could make small changes—such as editing text—and save them directly without sending anything to the chat. The Save button would create a new version of the project without triggering an AI generation or consuming credits.

design-save
design-save1698×262 5.12 KB

With the new Design Mode, I can no longer save these small edits directly. Even changing a single heading requires me to click Apply, which sends the change to the chat and consumes credits. On the v0 Max model, a simple change to an <h1> has sometimes cost me close to $1.50.

I understand that AI generations have a cost, but these are not always AI-generated changes. In many cases, I am manually editing text or adjusting a small property through the visual editor. It does not seem reasonable for every minor change to require a new AI generation.

Some people may suggest making these changes through the Code view. However, the previous Design Mode also made that workflow easier: I could right-click an element and jump directly to the relevant code. That option no longer appears to be available, so now I need to manually find the correct component or file before making a small edit.

This is especially frustrating because direct saving was functionality we already had, and Design Mode was previously promoted as one of v0’s strongest features.

Could the team clarify:

  • Why was the direct Save workflow removed?
  • Is there still a way to save manual Design Mode changes without sending them to the chat?
  • Could the option to jump from an element directly to its code be restored?
  • Are there plans to distinguish manual edits from AI-generated changes for credit usage?
2

Hi Romel,

I think your distinction is the right one: there is a big difference between manual visual edits and asking the model to generate a change.

From the current Design Mode docs, the expected flow now seems to be that changes stay as pending edits until you click Apply, and Apply “sends them to the chat” and creates a new version of the project:

So I don’t think you’re missing a hidden Save button based on the current docs. But I agree the UX is confusing if the original Design Mode expectation was “quick manual UI edits without spending credits,” especially for simple copy/style tweaks.

A reasonable feature request here would be:

Restore a direct Save/Commit path for manual Design Mode edits that only writes the selected text/style change to code, without invoking the model.

Keep Apply for AI-assisted instructions, screenshots, and structural changes.

The “jump from selected element to source code” part also feels important. If direct Design Mode saves are no longer available, then Code view needs a fast way to locate the selected component/file, otherwise small edits become much slower than before.

For now, the safest workaround for tiny copy changes is probably editing in Code view directly, but that is not equivalent to the previous visual workflow.