Things cost money. Slow requests are cheap. Fast requests are expensive. If you want fast requests, pay for them.
Iâd prefer to pay for the responses that are effective. I donât want to pay for responses where the AI forgets that it has access to the workspace, or decides to write python into *.cs fileâŚ
Last month, my 500 fast quota finished slowly. I was OK with working with Cursor. And when it switched to the slow mode, it was still OK.
I am in the second month now. 500 quota finished very fast. I donât think I used that much benefits of cursor. Actually, this month, cursor got crazy. It is not able solve errors, it doesnât do what I want. And it stucks on a loop that he repeats the same things maybe 10 times.
and slow requests are really extremely slow. Last month, a slow request was taking 4 or 5 seconds. Today, it is taking up to 1 minute. When I give a prompt, I leave the computer, do some tasks in the kitchen etc. and when I come back it is still waiting.
I donât think I will renew my subscription again.
Thank you.
4 Likes
I think you are forgetting that Cursor is basically a pump and dump buzzword scheme for venture capitalists.
Current slow requests with claude 3.5 for me are roughly 10-15 minutes.
half of the time they will be so long that I get timeout errormessages.
most of the replies are suggesting code that is identical to what is already in place, and that is at best. Because combined with bugs in Cursor, it also often tries to remove big chunks of code for no reason.
The AI model will often reply to a request with with a counter question like âwould you like me to suggest a solutionâ and when answering yes, it waits for 15 minutes then ask the same question again.
The AI model will also outright lie and say stuff like âI know I should answer with a solution but I am currently thinking about it, would you like me to think longerâ
its nothing short of a scam ran by 25 year old Elon Bros.
Iâm currently having a better experience using chatGPT or copilot.
1 Like
I donât know if itâs because a huge Queue in slow pool or new features but recently the time is SO slow i canât work rn !
2 Likes
Yes, IMO âunlimited slow requestsâ as a selling point needs to be reworded. Itâs misleading at this point.
Itâs more like âyou get some extra slow requests, and eventually it becomes so slow that itâs no longer usable.â They should also show some table of how many slow requests you get per each wait milestone (e.g. how many requests you get to do before waiting 1 minute, 2 minutes, 3 minutes, etc. per request)
1 Like
Yeah, I used up my 500 requests and tried to use the slow ones, but they didnât just seem slow⌠they seemed dumber, somehow. So I switched to usage-based and added $20 more. This thing eats up all of my requests on the same stupid errors over and over again no matter how much I update the .cursorrules file. Iâm not giving it another $20. I swear itâs gotten dumber with some of the âupdatesâ lately.
2 Likes
I am paying and it is still slowâŚ
Anyone know if creating a new account they treat your requests with a higher priority?
1 Like
this is not excuse for slow response. instead Cursor is forcing users to double their budge limit, otherwise even user increased custom budge limit, Cursor is still providing slow response.
Cursor should look for a way to low cost of tokens. Cursor is not even giving reasoning model in agent yet.
it looks Cursor has come to a point of stucking status: while users are not satified with the service quality, Cursor also has been able to find a way to improve its service ability.
1 Like
stop the cap dont take that long better than coding the wholething
o3 is a reasoning model and it is available as an agent. Technically Claude is as well, it just hides it in ant_thinking tags.
And Cursor canât make Anthropic or OpenAI lower their API costs. Sorry.
Cursos is bring anthropic fleets of customers who may otherwise not use the API. Deal based pricing is a thing and cost is going to be the limiting factor here, ultimately.
Itâs my third month with Cursor, and slow requests have become really slow. This is getting very frustrating.
1 Like
Extremely frustrating. Itâs so slow that it might not be worth it anymore for ME. Many prompts are wasted, not because of the way they are written but because of the inability to be resolved. Itâs a shame, its a fantastic product but it defeats the purpose having to wait for ever,
Im not sure why T1000 is so vividly defending this behaviour.
The problem is when you buy this you donât realize how slow it can get. I understand the architecture and why they need the slow requests, however, it doesnât seem like a fair game here. If i have to wait 5 minute for a wrong answer it really defeats the purpose, which is speeding up my development.
At this point, iâm inclined to give up the subscription until it gets better. I go through 500 requests very fast and i wouldnât have an issue with slow requests if they would be decent. But waiting 5 minutes for a really bad response its just pointless.
fully agree - when something like debugging gets into a constant back and forth, you can just feel the money being burnt.
hehe im not defending Cursor, perhaps you do not see all the posts / comments.
While there are often issues caused by users, the last few days issues are caused by Cursors suppliers or Cursor not having proper contracts and SLAs in place as it would be needed for such an operation at that scale.