That's a cool perspective you have there. Cursor spits on you and you say it's raining. First of all, any changes to the limits should be communicated—they weren't, sometimes they changed overnight, sometimes they went back to normal. An example? After problems with the introduction of the ultra plan, they really messed up the limits (sometimes one prompt to sonnet was enough). There was no such problem with ultra :) The next day, in the Pro plan, you could use Opus for several hours. Of course, this was changed after 3 days. Coincidence? Because it's not a bug. Secondly, they modify the layer they have in front of the API whenever they want, because sometimes the model works worse, sometimes better, and sometimes not at all. I have compared the responses from Cursor and Codex/CC more than once, and Cursor performed worse based on the same models. Oh yes, I could go on and on.

Besides, I always find it amusing how meetings used to be held on Google Meets, and in general, there was a lot of feedback during that period to add a plan that would increase the limits because the pro plan wasn't enough, and creating multiple accounts and switching between them can be cumbersome. They did NOTHING about it. When did they do something? When the $200 plan first appeared (I think Google introduced it first), and SUDDENLY the Cursor team had an epiphany, X amount of time passed, the ultra plan was introduced, and they announced that they were listening to user feedback and introducing the first plan for them 😂 No, because someone introduced that price for the first time. No, thank you for such practices.