I’ve been a Cursor subscriber for several months now, and I’m sure many other developers are also investing their money either to boost productivity, build their own businesses, or simply explore their creativity.
In the old model, once you hit the 500-request limit, Cursor didn’t block you entirely — it just moved you to a slower request pool. It didn’t cut you off. You could keep using it, albeit slower. Because of that, I used to burn through my 500 requests in just three days sometimes — who hasn’t? 
But with the current model, I’m frequently hitting the rate limit. And even though it’s still a great plan and I make frequent use of quick requests throughout the day, Cursor now completely blocks me — I no longer have access to the slow pool, which used to be a reliable fallback.
So what do I do when that happens? I temporarily switch to a competitor to keep my work moving. But honestly, it’s a frustrating experience to be forced away from Cursor. Let’s be real — using of mode “Auto” doesn’t solve most problems. The reduced context and downgraded model used for editing significantly hurt the quality. Cursor has become what it is today because of its great context management combined with Sonnet 4. So not being able to access that model feels like a major setback.
I’m in this boat tho, I’ve been trying to make better plans for less requests. kind of fun to have to aim your shots 
), and you’re right — it’s hard to find the same API value elsewhere. I just wish the fallback experience was a bit more forgiving like before. But thanks for pointing that out — I realized I worded it poorly earlier!