Do you have a chat link I can send to the team to investigate? I’m sorry about this experience.

Hi Pauline, thanks for a quick reply. Yes, it’s here: https://v0.app/chat/battleplan-fepKOSwQwoE

I hope the team won’t get offended by the language, because since the last update the work with V0 was very frustrating….

I’m right there with you. I’m having the exact same issues. I’m honestly about to give up on the new V0—the preview is terrible and constantly hits me with connection errors. I get what they were trying to do, but the execution is just a mess

Yeah, it’s getting more and more frustrating… especially with the new update when the auto fixing of bugs was removed…

From my experience, 🤖 v0 work best with clear and structured prompts.

Giving too many tasks at once can lead to confusion ⚡, and without defined steps, results may drift or affect unrelated parts. Breaking things into smaller, focused instructions ✂️ usually leads to more stable outcomes ✅.

Keeping prompts simple and scoped has made a big difference for me 🌟.

This is the way:

I've shared with the team anyway.

That’s what I’m trying to do most of the time… simple and specific commands.. and in case of something a bit more complex I always start in the planning mode and refine the plan before starting to implement it… and it used to work well but the last update just somehow broke it.

Yes DK, if the same workflow used to work and now doesn’t, that’s definitely something on the update side. there’s likely been a shift in context management or execution boundaries. Definitely worth investigating on the system side. Pauline P. Narvas Good that the team is looking into it 👍

Btw. the new diagnostic approach is useless. V0 doesn’t identify almost any issues. The auto-fix approach that was in the previous version was far more superior. I’m wondering why they changed it… was it to reduce cost?

I hear you, DK. It sounds like the new diagnostic approach is missing the mark compared to the previous version’s auto-fix. Hopefully, the team is taking this feedback into account, they might refine it or bring back some of the previous functionality soon.

Any update on this topic, please? @pawlean

I’m seriously about to give up on this. Look, I’m grateful for what this platform helped me build—I launched a successful project using v0—but now it can’t even handle the basics. It’s a total regression。It’s stuck in this infinite loop. It claims there’s a caching issue, says it’s fixed, but then the code fails to run. Then it apologizes, says it still sees the old file, and tries to fix it again. It’s just spinning its wheels and wasting my time。I really wanted to stick with it, but I’ve reached my breaking point. Since the updates after February, it’s been one loop after another. It keeps hallucinating progress while delivering broken code. I’m honestly done

Yes, I completely understand. I even explicitly told V0 not to mention cache issues anymore. What I’m seeing now is more of a regression in quality rather than any real progress. Over the last 3–4 days, I’ve spent over $400 just fixing issues that V0 itself introduced by modifying completely unrelated parts of the project while trying to fix something else. And yeah… Vercel won’t refund anything. At times it honestly feels like V0 is doing this on purpose just to burn more credits. I’m seriously considering moving to Claude + Bedrock.

Still no update?

Should I even expect any reaction from the team?

Is this the way the team is going to communicate with its customers?

I'm sorry for the delay, @dk-hello. This isn't the experience we want you to have! :( I can assure you this has been shared with our v0 product team who will continue to work on improving the platform.

Did you ever create a support ticket for a refund? Feel free to do so and link back to this post. I'll also send you a DM.

Hi, thanks for looking into that. Honestly it’s not about the refund. It’s really about the tool working properly. I really want to use V0 as it makes things easier but at some point a support from the V0 team is needed.

@pawlean I wanted to share my experience as well. The project management functionality of V0 so bad that I think I’ll be forced to move off and just build it from scratch using Cursor or Claude Code. Connecting to Github made it so I had to create a whole new project, so now I need to move all my domain settings from the old project to the new project. And just finding domain settings is a nightmare. Sometimes it shows up in the left sidebar (no idea how to consistently get there) and other times a dialog pops up but the dialog never loads. And for some background, I’ve been a software engineer/CTO for 30+ years. V0 has so much promise, but with this total dumpster fire I’m forced to leave. I’ll still be using Vercel for pushing our application, but I think I’ll be forced to have nothing to do with V0.dev. It really makes me sad.

Thank you for sharing your experience, @charliemorss! I'm sorry to hear that has been your experience.

I'd love to hear more on this, do you have screenshots of what you're seeing?

Thank you for sharing @charliemorss. Can you share more information about how connecting to Github required creating a whole new project? Did you already have a project connected to the chat before connecting to Github?

Hi Rickey,

Thanks for trying to make V0 better!

I created what I thought was an empty GitHub repo then tried to connect my V0 project to it. It gave me an small error message that wasn't very descriptive. I don't remember the exact wording, but it was basically telling me there was an error and that was about it. So, I ended up downloading a zip of the project and then creating the repo though V0 (I have no idea how I got to that particular screen) and it worked okay.

Just an aside, I think it would be really helpful if you all did more user focus groups and have them attempt to do basic things on V0, e.g. connect github after they've created a project, handle domain settings when not using V0 as the nameserver, etc. Your UI has just gotten so confusing I can't find anything. It's even harder to use than the AWS console and that's saying something!

Thanks again for your help, Charlie