On 4 May 2026, a v0 user posted to Vercel’s community forum that Design Mode — the panel Vercel added so people could nudge spacing and color without typing a prompt — had stopped touching his actual files. It instead “captures my visual changes as a JSON diff and screenshot” and “sends both to the AI as a ’translation task,’” he wrote in the Vercel community thread , and the round trip was landing edits in the wrong React components. One other user confirmed the same shift in the weeks after.
v0’s own documentation confirms this is by design, not a bug: applying a panel edit “serializes your edits … sends them to the chat, and generates an updated version of your project.” Figma Make, v0’s Design Mode and Lovable’s Visual Edits have all brought back the familiar sliders this year — but every one of them, by the vendor’s own account, turns a slider drag into a more precise prompt, not a direct edit to the file that ships.
The panel writes a prompt, not a diff
Figma made the same move last, and said so plainly. Its 30 July 2026 blog post announcing a properties panel and annotations in Figma Make frames the feature as a targeting improvement: “direct manipulation gives Make a precise target, instead of the searching and guesswork a text prompt requires,” and each edit “uses far fewer tokens and finishes faster” than describing the change in prose. Nudge the spacing between two elements, and the agent rewrites the underlying code to match. The panel only works on Make designs created after the update — on an older project, the prompt box is still the only door in.
That is a real gain for the designer’s afternoon, not just Figma’s compute bill. It is just not what “properties panel” used to promise, which was that turning a knob changed the file, full stop. Lovable got there first, walking back its prompt-only approach with Visual Edits in February 2025 , reasoning that “having to chat with AI for every small edit wasn’t ideal.” Eighteen months on, this is the same v0 and Figma Make that spent early 2026 racing prototypes toward production , and the industry has now agreed three times over that pure conversation was the wrong interface — without giving the file back to the hand on the slider.
The panel changed how precisely you could ask, not who holds the pen on the file that ships.
A product designer nudging padding in v0’s Design Mode is not editing the component her team will deploy. She is issuing a tightly scoped instruction to a model that will rewrite that component on her behalf, and checking that the two match is now a step in her workflow rather than an assumption underneath it — a small tax nobody itemized when the sliders came back.
What the panels still can’t show you
The strongest case against wanting more knobs, rather than a different kind of transparency, comes from “Rethinking the UI of GenUI” , a study pitting a conventional conversational tool against a structured-input prototype across 24 UX designers and product managers. Structured input “surfaces key facets but requires more work, raising entry barriers to start exploration,” and despite its honesty about intermediate steps, professionals still preferred high-fidelity conversational output because it matched what they expected from AI-generated work. Precision costs something; the panels bet that most edits are small enough to absorb that cost.
What a separate research prototype suggests is missing isn’t more structure but a visible trail of what the model decided. LegoUI , published 4 August 2026, stages generation along design dimensions and logs each step in a format “enriched with provenance,” letting a designer accept, reject or amend one decision instead of re-describing the whole thing. Across 40 design prompts and a user study, participants “reported significantly greater transparency, controllability, and alignment with their intent compared to existing one-shot generative UI tools.”
Neither paper nor documentation puts a shipped properties panel through the same test — nobody has run knobs against a decision log head to head on a real project. But set the mechanism the vendors describe next to what the research prototype’s users responded to, and the industry’s move reads differently: it restored the control surface without restoring what that surface used to guarantee.
Read across, the ingredient the system that tested well for trust actually had — a record of what the model chose and why — is exactly the one no shipped panel offers. That is a step this article is taking from a mechanism description and a research result, not a measured comparison, and it is worth holding loosely.
The same gap between a tool’s stated reasoning and what lands in the file showed up on the code side of this problem earlier in the summer , when AI design tools’ own explanations for a decision were missing from the generated code in more than a quarter of cases. A slider you can trust to describe your intent accurately is not yet a slider that shows you what happened next — and until one of these tools ships the second thing, the first is only a better-worded request, however satisfying it feels to drag.
