when i ask v0 what the problem is, here are its typical answers, but then it carries on and does the same again and breaks things, any help, feedback and advice would be greatly apreciated You're absolutely right to be frustrated. Let me explain what's been happening and how we can fix this properly:

The Root Problems:

1. I've been overcomplicating things - Instead of making small, targeted fixes, I kept adding more and more debugging code and endpoints, which cluttered your project and introduced new issues.
2. Too many experimental changes at once - Each time we tried to fix something, I added multiple new files and complex logic instead of just fixing the one specific issue.
3. Not respecting your working code - You had a working version (v828), but instead of making minimal changes to that, I kept rewriting large portions.

This has happened to me quite a bit.

One way you can keep it from doing this is the ask it not write any files without your permission. That will at least give you a chance to see what it is going to change

Started happening to me a lot as well recently. It started touching files that are completely out of context and breaks things that worked just fine.

I even requested to refund credits because it was taking too many loops so it apologized and pretended to pass on the message internally - but it didn't.

Any updates on this is v0 due to make any type of statement explaining what is going on? as I have halted further progress on my project until I hear something, is this NOT the place where v0 will respond ? if so does anyone know where and how i can listen out for something from v0 support to advise us what to do? Thanks for any feedback

It sounds like you're working in a project with a very high number of versions (828+ based on your earlier comment). That can cause slowness and messy context, which often lead to the sorts of changes you're seeing and want to avoid.

If there's a version you're happy with, I recommend going back to it and forking from there. That will help with the context issues that can lead to overly broad changes.

Once you have it in a new chat, changes should be more in line with what you're hoping for. I recommend using using very specific commands, inline code generation, and design mode to make sure changes are limited to specific targets.

Thanks very much for coming back to me, yes the project had a very high number of versions because things started to go wrong from about version 600 plus, needing try and try again numerous times. Anyway i have now forked as you advised, having first removed all the debug code before i forked, so the new chat and code is a lot cleaner and things are getting better, not so many mistakes.. Also for others to know what has also seemed to help is that in the PROJECT i have i have defined some project rules, which have been saved correctly for the project to refer to each time a new version is created. The rules i implemented is for v0 to only use in-line edits or quickedits on new versions UNLESS i specifically give it permission to do full re-writes, this seems to be helping stop breaking the system, it has definately helped stop the numerous re-writes that v0 was doing. So thanks for your help and i hope the above helps other avoid the huge frustration that total re-writes was causing.. cheers