Hi Amy, this is great in principle, but it’s hard to get excited about new v0 capabilities when the current v0 editor has been broken since the last upgrade.

The bug has already been reported (via feedback channel and through community), yet there’s still been no meaningful update or ETA for a fix. Before promoting the next big workflow, it would be good to see the existing core experience working reliably again — and to hear clearly from the team about when that’s actually going to happen.

https://community.vercel.com/t/v0-editor-issues/49664

Vercel Community

V0_editor_issues

Hi All, Since the last upgrade - the v0 editor has regressed: source files are no longer directly editable, and image assets that were previously previewable...

Any news on this ?? I don’t think anyone is even looking at this and so I’m going to escalate it on Twitter and other forums.

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 Dyad, Bolt respect our workflow. Bring back the code editor

I believe your decision to remove direct code editing in v0 is extremely short-sighted and blatantly profit-driven. To update simple details on a page, I now have to go through the chat and consume credits, unless I rely on external tools like GitHub or VS Code.

This does not keep users within v0; it pushes them to become independent of it. What was the rationale behind this?

I believe this change will decrease your revenue rather than increase it. Please reconsider this step and let us work inside v0 as we did before. Thank you for your time and attention.

All - Given the lack of updates or lack thereof - it sounds quite deliberate. If this is their cunning plan, rest be assured that's it's going to fall flat on its face as users will leave them in troves! I hope someone can talk sense into them, but then again, common sense isn't so common after all !!

Without manual, basic code editing and without file management has become useless and forces conscious users to look for an alternative.

@samssharma-7158 @sumonmaity @colwalkurtz-7852 @greguarr I hear you and understand your frustration. However, these comments aren't related to the Meta Immersive Web SDK starter app topic. Let's keep the v0 editor comments in the feedback thread to make sure the team can see everything you want to say

https://community.vercel.com/t/restore-manual-code-editing-immediately/49772

Vercel Community

Restore Manual Code Editing Immediately

Credit & Time Waste: Spending generation credits and waiting 30–60 seconds just to change a tailwind class, fix an import path, or adjust an environment...

Thanks for the heads-up, Amy. Everyone, please share your thoughts on the main feedback thread so the team sees how crucial manual editing is https://community.vercel.com/t/restore-manual-code-editing-immediately/49772

Vercel Community

Restore Manual Code Editing Immediately

Credit & Time Waste: Spending generation credits and waiting 30–60 seconds just to change a tailwind class, fix an import path, or adjust an environment...