Why Is Traditional Mode Also Affected by Speed Limits? How to Choose?

I am currently using the traditional 500 requests mode. However, I am also affected by rate limiting. During certain periods, the speed is so slow that it is almost unbearable. If that is the case, what is the point of falling back to the traditional 500 requests mode? The Cursor team currently provides a very opaque model. It seems that no matter which mode is chosen, the user experience is not good.

I think there is no more 500 requests limit . It depand on hwo much resources you ues , and new model cost quite expensive.

@Wu_Felix the legacy plan has no rate limit and is limited to 500 requests but there is no slowdown from Cursors side. If you have issues with any model please file a detailed bug report so the issue can be investigated.

I opted out of the Plo pran new pricing and hit rate limit after a few days.

I only used 92 requests so far

Version: 1.2.2 (Universal)
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:07:27.002Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin x64 24.5.0

this is likely the provider e.g. anthropic limiting cursor, if all i read here is true. i heard one competitor complain about anthropic’s rate limits as they allow only certain amount of requests to their api per minute, were you using claude at the time?

1 Like

That is the the Anthropic internal rate limiter due to overload. Not your account rate limit.