I’ve run out of fast-request credits on Cursor, so I’m now stuck using slow requests—and it’s been a nightmare. In particular, Claude-3.7 Sonnet takes forever to respond. Every time I send a prompt, I’m looking at wait times north of five minutes, and on busy days it can stretch past ten minutes before I even get a first reply.
At that pace, a single question-and-answer cycle can easily monopolize a half-hour of my time. I can’t iterate, experiment, or troubleshoot in any kind of reasonable workflow. It feels like I’m back in the dial-up era.
I understand that slow requests are lower priority, but this delay makes the tool virtually unusable. I’d love to have either:
- A guarantee that slow-request latency stays under, say, 1–2 minutes
Right now I’m hesitant to keep my projects tied to Cursor if the only way to get anything done is to watch the loading spinner for ten minutes straight. Anyone else running into this? Has anyone found a workaround, or can Cursor please consider improving slow-request throughput?
