today , cursor reponsed so slowly, always took about 1 minute ;
i tried to open new chat ,but it did not work.
1 Like
Hey, check out your acc setting:
maybe you ran out fast requests?
take a look here for more info:
i have ran out fast requests, but i think it’s not the reason, because i ran out fast requests 10 days ago, but cursor responsed too too slowly today
I found that cursor now fixes the slow request setting for claude 3.7 models to take 90 seconds to start responding. This is really too bad.
1 Like
oh !!! I finally found that it responsed so slowly only switching to claude 3.7 model , that is so bad!!!
I think you need to change this setup via cursor setting since its change automatically when you change Modes/open new chat to same model
Just to clarify here, Claude 3.7 should have the same slow pool logic as Claude 3.5.
When it was first released, Claude 3.7 didn’t have the correct logic in place for users using slow requests, which may have unfortunately set the expectations of how fast the slow pool would response.
This has been fixed for a few weeks now, and as with all requests to the slow pool, the time each request takes gets slower the more you use it.
Besides enabling usage-based pricing, and purchasing more fast requests, my best recommendation would be to use non-premium models more often, like DeepSeek v3, as Claude 3.7’s intelligence is often overkill for simple changes!
but why my coworker’s cursor did this quickly, only mine behaved slowly , and we are business pricing.
If you have used your request allowance, as shown on cusor.com/settings, you will end up using slow requests for those made outside your allowance.
Each user has 500 requests by default, so it’s likely you have used more requests than your co-worker, and have hit your usage limit before them!