I am a Pro user of Cursor. when I hit the 500 limit of premium, it got slow like I had to wait one day for each request. why do they take $20 if that’s what they do? I understand the meaning of slow request but that slow? It even stuck for hours if found lints errors it made
Hey, when you hit the slow pool, you should be shown an alert in the UI that says you are in the slow queue, and how long you will have to wait, which isn’t appearing in your screenshot.
Is this still happening with requests now, and does it continue to happen in a new Composer session?
I got the same behavior but it is not linked to fast or slow request. I have the impression that when a “found lints” situation occur, cursor is stuck. Don’t know what to do on one of my projects.
1 Like
Can you try disabling the linting feature in your Cursor settings, and see if that helps?
I’ve done this, but though I disabled the 2 Lint functions, Cursor still identifies an error in a php file and loops on generating nothing … with this file name as context. I tried many things like changing the context but it always come back to this behavior.
Hey, can you send a screenshot of this? If the Linting fix step is disabled, Composer shouldn’t see or attempt to fix the errors.
It still stuck even if create new.
stuck for more than 5-10 mins.
Note: I have latest version installed. a pro user. used premium quota.
The slow composer now more slower taking longer than usual(in non premium requests).
I understand we should wait but that much wait? ufff
Hey, the slow pool can be very slow when using Claude 3.5 Sonnet during peak times.
I’d recommend using another model, like DeepSeek v3 (enabled in your settings), which performs similarly to Claude 3.5 Sonnet without being a premium model, and therefore needing to queue!
Sorry, DeepSeek models do not yet work on Agent mode, but we are working on support for this at the moment, and it should be available soon!
1 Like