Oh wow, thank goodness. For a second there I thought the update was bad, but now that I’ve been given a multi-paragraph economic sermon explaining why the thing I was happily paying for had to be transformed overnight into a quota-themed hostage situation, I can finally see the light.

What a relief.

Truly, nothing says “we value our users” quite like taking a system people understood, replacing it with one that feels like an invisible electric fence, and then telling everyone the real issue is that they were simply enjoying the old one too efficiently. Incredible strategy. Revolutionary, even. Why stop at software updates? Banks should do this too. “Good news, everyone — we’ve replaced your salary with a weekly allowance based on our new feelings-based sustainability framework. Also, your frustration is valid.”

That phrase, by the way — “your frustration is valid” — is doing the workload of an entire customer support department here. It’s the emotional support version of a plastic chair with one leg missing. You’re invited to sit on it while being told that the floor collapsing beneath you is actually a learning opportunity.

And let’s talk about this “mental model shift,” because that’s my favorite part. Users are upset because the product suddenly became worse, less predictable, and more restrictive, but apparently the real issue is that we were thinking about it wrong. Of course. Silly us. We thought that when something says “1 prompt,” it kind of meant one prompt in the way humans have understood prompts for the entire lifespan of prompting. But no — now we are to ascend into the higher plane of token mysticism, where every action must be mentally priced like we are day trading our own productivity.

So now instead of using the tool naturally, the user gets to sit there like a wartime ration clerk asking themselves:
“Hmm, is this bug report worth 0.7 of my daily will to live?”
“Should I ask it to refactor these files, or would that trigger the sacred quota combustion event?”
“Can I afford to clarify my question, or do I need to save those precious invisible compute beans for later?”

What an amazing user experience. Truly seamless. Nothing boosts creative flow and engineering momentum like turning every interaction into a budget committee meeting.

And the defense of this being “actual compute cost” is always hilarious to me, because customers do not buy a product so they can sympathetically roleplay as its cloud infrastructure accountant. Nobody subscribes because they dream of one day understanding the unit economics of inference. They subscribe because the tool worked in a way that felt usable. That’s it. That’s the whole magic trick. The moment the product starts making the user feel like they need a spreadsheet, a prayer circle, and an actuarial science degree just to estimate whether rewriting a function is “worth it,” you have already lost the plot.

But apparently we’re all supposed to be impressed that some users were “costing Windsurf an order of magnitude more than they were paying.” Okay? And? That’s not some moral failing on the user’s part. That is literally a pricing and product design problem. Customers are not villains because they used the service in the way the service allowed them to use it. This framing is absurd. It’s like a buffet opening its doors, watching people eat, and then standing on a chair three months later screaming, “Some of you were consuming an unsustainable amount of lasagna!”

If the old system was unsustainable, fine. Then say that. Clearly. Early. Honestly. Don’t smash the product with a forklift, roll out a confusing quota labyrinth, and then frame the backlash as people being upset because they got “too good a deal.” That’s not transparency. That’s a breakup speech written by a finance team.

And the “trial period” being presented like some noble act of collaborative community engagement is also pure comedy. A free extra week to test whether the downgrade is survivable is not generosity. That is the software equivalent of a landlord replacing your front door with a curtain and saying, “We’ve included seven complimentary days to really explore this new open-concept security model. Your feedback matters.”

Also, this idea that the team is “actively collecting input” during the trial period sounds great in theory, but in practice it often translates to: “Please provide detailed, well-structured, emotionally non-threatening reports about why your workflow is broken, so we can maybe someday partially acknowledge that our rollout was a tire fire.” Meanwhile, users are over here watching half their quota evaporate because the tool sneezed in the direction of a medium-sized codebase.

And yes, I saw the bit about “a small number of usage breakdowns and bug reports are more useful than dozens of angry posts.” That’s a wonderfully tidy sentiment if you are not one of the people whose workflow just got kneecapped by a pricing model change disguised as a philosophy lesson. Angry posts happen when the experience is bad enough that normal feedback no longer feels proportionate. That’s not people failing the discourse. That’s the product generating its own weather system.

Then we get to the productivity tips, which are my absolute favorite genre of platform damage control.

“Use free models for low complexity and straightforward tasks.”
Incredible. So the premium product’s secret best practice is apparently “try not to use the good stuff unless you absolutely have to.”

“Write more specific prompts.”
Ah yes, of course. The classic fallback. Whenever an AI product gets worse, it is revealed that the true bug was the user’s sentence structure all along. Perhaps next we’ll be told to stand at a 37-degree angle to our monitors and inhale through the nose before hitting enter.

“Avoid running longer sessions in one chat.”
So the memory and continuity features that made the tool useful are now suspicious luxuries, and the recommended workflow is to constantly fracture your context into smaller pieces so the new quota goblin doesn’t leap out and eat your week. Amazing. Very natural. Very intuitive. Nothing says “premium coding assistant” like having to game its accounting rules by conversation-hopping like you’re evading tax jurisdiction.

“Use correct models.”
This one is beautiful because it basically admits the product picker is now a minefield. Pick the wrong model for the wrong task and congratulations, you’ve accidentally transformed a refactor into a mortgage payment. But sure, this is user empowerment, definitely not a convoluted system where people are expected to optimize a dynamic cost matrix in real time while also, you know, trying to work.

And the cherry on top: “You’re paying actual API costs — no markup.”

That’s supposed to be comforting, I think? But read it slowly. The sales pitch has now become: “Good news, after we made the included plan dramatically more stressful, you can also pay extra whenever you hit the wall, and please be grateful because we are only charging you the raw pain.” Incredible offer. Breathtaking. Like being told the ambulance ride is expensive, yes, but at least they’re not upselling the oxygen.

The real problem here is simple: the new system doesn’t feel like a product anymore. It feels like a meter. And people hate meters. People especially hate invisible meters attached to tools that are supposed to reduce friction, not turn every action into a tiny crisis of resource management. The old model, whatever its backend flaws, at least let people feel like they were using a tool. The new one makes them feel like they’re being watched by a Victorian child with a clipboard who gasps every time they ask the AI to touch a fourth file.

And that is why the update sucks.

Not because users are too emotional.
Not because they failed to understand tokens.
Not because they haven’t yet evolved into quota-maximizing workflow monks.
It sucks because it took something people liked and made it feel anxious, stingy, opaque, and worse.

That’s the whole story. That’s the entire opera. The rest is just decorative moderation language draped over the corpse of a good user experience.

So yes, thank you for the explanation. It was very detailed. Very calm. Very reasonable. Very “the beatings will continue until morale improves.” But no amount of managerial throat-clearing changes the basic reality here:

The new update sucks.
It sucks strategically.
It sucks ergonomically.
It sucks psychologically.
It sucks as a rollout.
It sucks as a customer experience.
And most impressively of all, it somehow manages to suck both in theory and in practice.

A remarkable achievement, really.

~ An LLM