Rate Limit Observations, Let's Talk

Discussions
1

Ok, since Cursor staff is oddly silent and showing current ambivalence about talking to us about this currently let’s pool some observations.

Sonnet 4

Yesterday was probably an outlier. I had at least ~40 requests for the day until I saw the Rate limit. Then after a couple hours I got ~10 more before bed.

Today I got ~5 in, ~4 hour wait, ~9 in and I’m now at another ~4 hours waiting to see if I get more.

–edit-- after I posted this it has unlocked for 1 request.. so about 5 hours to get 1 additional request. :laughing:

What have you seen, make sure to include the LLM you are using, how many requests you got, how long you had to wait for a “recharge”, and then how many you got until the next limit.

I’m not interested in token utilization or context windows, this is a back of the napkin math concept here. Sharing is caring and at least we can see if this is an even bias of maybe there are buggies running around.

6 Likes
2

Could the Cursor devs please comment on this? I’m just trying to figure out which day was the “normal” one by design and which was a bug. I understand new pricing can have glitches, but I’m really not sure what the endgame is supposed to be. Because what he’s talking about (and showing) with 1 message every few hours sounds awful.

3 Likes
3

up!

4

If you’re not interested in tokens and context windows, you might have a hard time making some sense of these rate limits. It’s been suggested by devs that they depend on compute usage rather than on raw request numbers. Which explains why some users get plenty of requests and don’t hit the limit, while others reach it very quickly, even when not using MAX mode.