v0 auto-diagnosis automatically editing code and creating new versions without consent

v0
, , ,
1

Problem

Can someone please help, who ever decided to push a new release with auto-diagnosis needs to re-think this.

Current Behavior

I have probably 200 apps in my favorites list, I open one up for a client today to work on and all of a sudden it just starts writing edits and breaks the entire Fricken application. It shot out an entirely NEW VERSION, WTF IS UP WITH THAT?

I open another client app, and same thing, as soon as I open it it starts running and changing all my code and BROKE the APP…

  • I have no idea what was done, no way of checking, NO WAY of turning this AUTO-BS off.
  • I now have 198 other apps to go check on as a company and am going to opne each one and have them do some bullshit that I didn’t ask to have done, I didnt command to be done, nor did I APPROVE to be done.
  • Its eating credits, its creating versions for no reason and any type of organization that a larger company like myself has, its completely GONE.

Even if you ask it “hey, can you do a quick scan and see if I have any vulonerabilities.” Cool, 2 days ago it would scan tell you what it found and Id go fix it. Now I cant even do that because as soon as it done telling me about it, its just “AUTO-DIAGNOSIS” and FIXES stuff that I haven’t told it to do.

I can pull a git version back in, but as soon as it comes back in, the auto-diag starts all over again, so its a big loop.

We are a team of 6-8 depending on projects, we have everything split between a few accounts, we can not take a chance checking in on anything that we may have local here in Vercel because of this Auto-Diag.

This is unreal!

2 Likes
6

And then here is the best part: Go ahead and roll it back to the previous version, as soon as it gets done mounting, the auto-diagnosis kicks back in, changes what I had again, and then pushes out another “Fixed” Version.

Did anyone ever think that a developer may have scripts running that doesn’t sit pretty in a serverless environment, but works fine when they actually put it on their own server?

Im sorry dont mean to rant, but this is ABSOLUTELY BONKERS… Not even a warning pop up with the option to have it auto-fix or keep it as it was.

We are afraid to check any of other other accounts or pull any code back in to work on right now and have gone back to just working locally in our VS, which is fine I guess, but man this is an absolute shit show with this auto-diagnostics just firing..

1 Like
7

Another bug: I opened up a new chat, just to see how this is working, I ask it to set my up an application with a specific database structure, it thinks, then gives me a few options to select or to tell it something else, COOL!

Well you cant select anything because the “AUTO-DIAG” is running and checking the application, and ZERO has been built yet. So I have to wait for that, then it creates me a new version, of NOTHING, and then I can finally select my option. Vercel starts building etc. etc. Its a loop!

1 Like
8

image
image1344Ă—1158 67.9 KB
went from working production applications to ones that now cant even publish or show a preview. THIS IS UNREAL !

1 Like
9

image
image476Ă—526 20.5 KB

Another example, this app hasn’t been touched in 24 hours. When we left it and pushed the update, there are zero errors in a production environment, this one has to do with Lint. So we dont mess with those errors because sometimes it can break the working application. Well as you can see 2 hours ago, it updated the version and is waiting for me to push it.

If I try to roll it back to use the version that “I WANTED” it to use, guess what, it makes it worse, and it goes back into diag mode again and starts fixing it again.

Considering we have quite a few applications like this, were stuck. the only options we have right now is to pull the code down from git into our VS and work on them or pull them into another IDE.

I cant not believe there hasn’t been a single response on any of this or that we are the only ones experience this?

1 Like
10

And you have no idea which version you have published anymore, its gone? So one of the three versions from 24 hours ago is the right one, doesn’t neccesarily mean its the last one, could of been multiple people working on it and had one published and didn’t publish the new one yet.

I have a few other apps that show me multiple PUBLISHED versions, so again who knows which one is the actual published version.

Anyone have any ideas? Even VO is telling me to turn it off in the right panel, but there is no right panel to turn it off?

image
image318Ă—299 9.3 KB

1 Like
11

image
image302Ă—882 35.1 KB
So then it knows im pissed, it asks me to choose, I chose A and its start doing the auto-diag again.

I have one specific app that hasn’t been deployed to git yet, now I cant because it will only deploy the “New Versions” that the auto-Fix have created. Unless I know or wrote the code, why would I want to publish a version that I didn’t make or ask for changes to be made. Now im stuck with an app that I cant publish the right version, if you pubish the one vo created and then restore the one you want, the auto-fix starts again and puts ya right back in the crap situation you were in to begin with.

30 years of coding, ive never been in a mess like this before.

1 Like
12

I totally understand where you are coming from, its such a weird thing that it just starts changing things without telling it to do, even worse that its really unclear which version is the auto version etc etc. this should deff be a opt in or opt out option. I can understand that it can be a nice feature for a beginning vibe coder. But if you have more experience this is just something really ennoying and credits wasting.

1 Like
13

For every prompt that i send it also finishes with the auto-diag check, and with this 1 project i get this;

image
image754Ă—220 7.49 KB

Its basicly saying in dutch”this is only a deprecation warning, not a crash/error - de app just works normally, no action needed” and its not even showing the warning that its talking about so i dont even know what the context is. @anshumanb is there any way to opt out for this? Last time i also had a project that just broke down, same problem @devglyphx-6325 is facing.

1 Like
14

This problem is driving me insane. No matter what my prompt is, auto-diagnosis takes over → changing, reverting, changing, reverting, creating new versions without actually properly adressing my prompt. It feels like my only option now is to wait it out until this auto-diagnosis is removed, because auto-diagnosis keeps on taking over the conversation and creating new versions.

1 Like
15

Hi everyone, I’m sorry that this is causing trouble. Let me take this feedback to our team.

4 Likes
16

@marnix-3108 and @devglyphx-6325 could you share the chat URL for the ones where it affected the most?

3 Likes
17

Hi Anshuman, thanks for letting the team check it, i need to see if i can find back the project, deleted some projects yesterday en this morning because of the other bug with the sandbox. Will see if i can find it. But besided that, it just feels really bad that a ai takes random control of your project, that just shouldnt be happening. We all love AI, but we as humans should always be in control, epecially with custom projects with special routes where you maybe dont really follow best practise, but it only works in that way. Anyways you get my point i think. It should be a on or off button/switch in the project or chat settings.

1 Like
18

I didnt find the old project that got ruined, but i have a other sample in my current project; https://v0.app/chat/creditchecken-budget-tracking-app-bRxDfQbnUI8 (i am working in it right now)

The last 3 or 4 prompts it started up the auto-dia and everytime it comes with the same results that it “fixed” something, but with the next prompt it just states the same again, its a mess. and it also just burns my tokens with every single prompt that i send.

19

Good morning @anshumanb , thank you so much for looking into this. I am currently on the Road, I’ll be back at a desk in about 2 hours and I can send you whatever your need. I stopped opening projects and told my team to only use VS for the time being. I dont have one specific link, its every one of them.

The issue is, that its trying to correct errros that someone like myself, already knows exists, but also knows that they dont exist in a production enviromnet, especially if you are doing any web3 work.

So as an example (Sorry at light trying to hurry), any app that we had built that utilized a Meta Mask, or Blade, or anytype of web3 wallet, as soon as you would open one of the chats, it would start to auto diag. Instead of just removing the lint, which doesn’t need to be moved, it started make changes to wallet files and everything else, trying to “find” all instances.

Up till 3 days ago, this never did this, so it has to be something from a recent push. Like I stated above, its a big loop!

  • Login in open chat
  • Chat immediately starts to diagnose and create a new version
  • You try to restore back to the previous version, it does it, and then the auto-diag starts again.
  • This time making the same changes, some different than the first, and putting me back in the loop.

My team and I are literally at a stand still, not because we dont know what were doing, but because we’re afraid to open any of the other projects / chats we have across all of our accounts.

So any info, any update info ANYTHING, would be extremely appreciated!

3 Likes
20

Thanks both of you for writing this feedback. I’ve forwarded to our team and will relay back what the solution is for this.

2 Likes
21

This is happening to me too, this is very frustrating, I have tons of work to deliver and I did 30 versions of the page fixing things I didnt asked to change, this is taking me credits out, time out and im getting behind with deliveries for my clients, also, I give it a very specific prompt to it and the app does one or two things out of that prompt, this is a huge error. And it’s generating us a lot of trouble.

1 Like
22

I am seeing the same thing, wasting credits and breaking code. Restoring sometimes failed breaking code beyond repair.

1 Like
23

Hi @jerry-2306, is it happening on old chats or only new chats and messages?

@devglyphx-6325 @marnix-3108 our team has pushed a change yesterday so it doesn’t happen for existing chats or old versions.

Could you share chat URLs for us to further debug this?

2 Likes
24

Ok try to follow me on this: I opened up an test app that I was messing with from a few days ago, someting I dont care about. When it opened it showed, No errors , like it diaged or something. Then I started to ask it a small question and told it no changes, it spit out an answer and as it spit it out, it waited for a preview, diagnose it, no problems. (That is the problem).

Then It asks me if I want it to go ahead and make it full color as you can see from the images. I respond with sure. Code gets done, you can see it starts to diag again, then says no errors. (Question is if there are no errors or there just not being auto-fixed). Anyway… the last image, you can see that the globe, which should be multi-colored, didn’t change at all. Any other version over the last year, would of changed the color, updated the preview and been ready to publish.

There are a number of issues happening with Vercel that haven’t been present in previous versions. Another example, we have a client that needs an HTML5 game turned into a blockchain app, normally this takes me 30 minutes to get situated enough to pull off stick in VS and finish it. Tried to test tonight to see if it was any better, it ran for almost 12 minutes and then spit me out an app as a white page, and then got in a loop trying to figure it out, all while eating credits.

Heres another one: an employee today, went in and tried to have it write a simple login page utilizing hedera. I build quite a few Hedera applications, and normally I can come to a chat and Say use walletconnect with connector and use it for authentication or something simple, just to get the base quickly written. Normally It may take me 2 or 3 max, chats to get everything nice and pretty; tonight, same as above, same prompts (we save prompts), and it started to build it completely wrong, wouldn’t install the packages, couldn’t publish it, and every time all it did was keep trying to auto-diag and it kept making it worse.

Something is severely off to the point we may have to just call it day and move on to another platform, there are hundreds of chats between us, and not just the auto-diag and fix stuff, it just seems like it got dumb over the past 3-4 days, so much so its quicker for us to open VS and just grab some code from co-pilot as we go. I know that sounds crazy, but Co-pilot been giving us better results than V0 ever since Ive been posting about the issues. I know its not a claude or sonnet problem because i have clusters at my office and there are running fine. Same command, same results.

Suggestion: Maybe the devs should give users the option to upgrade to newer versions when they are released or at least send out an email to everyone letting them know that updates are being pushed and performance may be degraded. (Try a prompt on a Saturday vs a Prompt on a Tuesday for example)

Anyways, it just really sucks and I’m starting see that I’m not the only one that is being affected by these changes.

I do appreciate your efforst! id give you a link but i cant publish it.

Oh also, the errors are stacking up, especially around Turbopack. Ive haven’t seen that error once in the past year, now it seems like every app I have on here has it and is causing stuff not to publish.

image
image1259Ă—982 60.3 KB

image
image1920Ă—1004 672 KB

image
image1137Ă—377 34.5 KB

image
image1203Ă—897 61 KB

1 Like