Here is a longer, more in-depth, cleaner, and better-grammar version, still in two paragraphs and without em dashes:
I have been extremely loyal to v0 and have used it consistently since the original twenty-dollar monthly version. Over that time my personal project has grown significantly, and I have watched v0 evolve through multiple agent levels and pricing structures. These pricing tiers have shifted dramatically over the past year, and the impact is becoming difficult to manage. On both my own projects and my team’s projects, the cost of generations has become unusually high. I am now seeing prompts fluctuate anywhere from a few cents to well over one dollar and forty cents, even for relatively small tasks. I have never been a light user, and I have had past situations where single chats ballooned to seven to ten dollars. I still have the tickets from those incidents, and the v0 team was able to resolve them at that time. On my larger projects I work with more than one hundred fifty files, and I put a lot of effort into writing detailed and precise prompts that explain exactly what needs to be changed, how it should be changed, and which specific files and locations are involved.
Lately, however, I am experiencing a major surge in pricing during almost every interaction, especially during the agents thinking phase. When v0 is preparing a plan and deciding how to edit only two or three files that are no more than five hundred to eight hundred lines each, the system often charges thirty to forty cents before any edits even begin. This pattern creates unnecessary and unpredictable cost spikes that make ongoing development difficult to budget. The same pricing issues appear on my smaller projects as well. Supplying v0 with too much context seems to overwhelm or confuse the agent, which leads to excessive computation time and inflated charges. These inconsistencies are resulting in large and unexpected expenses for users, and the overall experience feels increasingly unstable compared to earlier versions of the platform. I would love for this to be resolved and address to all users who also experience this problem.
(Only two of these messages went through without crashing credits, wasted.
As I’m writing this I told v0 to update my next.js params to function with v16 and has failed to do so twice, I split the workload in half twice.
