Thanks @amyegan, unfortunately the response doesn’t answer our questions or concerns.
Like many others in this thread, I’ve been a paying member of V0 and introduced it to my team of PMs and Engineers. We’ve incorporated it to our workflow, we’ve seen great improvements in V0 over time as you delivered new features, increased model quality and more. The output that we were getting from V0 was a game changer and made our work with your product enjoyable and valuable. The point of frustration as mentioned time and time again across the forum, is that this changed once agent was introduced. What happened? Quality went down, reliability went down, and the effort to produce a design went significantly up. The product became less valuable but the price increased.
-
“The shift to Agentic v0 means no more need to choose models.” Why remove user choice? Other products (for example, Cursor) lets you pick either an Agent or a specific model. A dropdown with three options is not a UX burden, especially when it produced better results. If the goal was to simplify, why force a lower-quality default on users who relied on the previous behavior? Introduce Agent, place it as the default choice, and if a user wants to he can choose one of the previous three models.
-
“High credit usage is often the result of broad instructions, big files, or large projects. Forcing the agent to scan every file for every command isn’t the most efficient use of resources. Instead, breaking a project into components and targeting specific changes helps manage context and reduce credit usage. And be very specific with prompts.” This might be the case, the problem that we’re trying to highlight is the fact that it wasn’t like that before. We didn’t have this issue, I can run an old prompt against agent and compare the results, the previous output (running against a model) was way better, it’s not even close.
I now need to spend significantly more time, to get mediocre results, while just a few months ago I would get amazing results in a fraction of the effort. -
“Code output will vary based on project settings and instructions provided. Setting project level instructions and strategic forking can get you more predictable results. Giving targeted instructions also helps.” My previous point above stands here as well. If this was the default state of V0 that would’ve been a different conversation, the problem is that it wasn’t like that - it gotten worse.
Our main point of frustration is that we had an amazing product, that we used daily and generated value repeatedly. The product quality has significantly reduced to the point where it’s unusable, because we are forced to use agent that is simply not as good as the previous models. You had a great feature, it was amazing, you took it away - the users are frustrated. This is not abnormal, this is a normal response to a decision that you’ve made that doesn’t make any sense to the users. They get less value, spend more time, and pay way more money, because of a single feature.
Thanks for you response, I’d like to again point out - this is all coming from place where users had an outstanding experience with your product. The results your product produced were a head of all competitors, you were on a completely different level. This is no longer the case because of Agent, hence we’re frustrated. You gave us something amazing, and then took it away.