Hey. This is probably gonna sound insanely stupid but I have an actual use case. As we know, you get 500 fast requests per month. Can I switch between using fast and slow?
My use case here: I (sometimes) like to play a little game while waiting for Cursor to do its thing. It’d be nice if:
Yes, the fast requests make me rush it all. I don’t know why.
Thanks guys
It’s a win-win because: I bet I’d use 10% of the fast requests, which speeds up things for others and makes your rate limits more chill. And I get to keep things slow as I want
+1 to this. Was just wondering the same thing. I work on more important projects during working hours, which fast requests are good for. For more hobby-ist/testing stuff like on weekends, I’d rather not use my fast requests on this (but still use a powerful model).
From first principles, it seems odd that determining whether to use a fast request is based purely on the first 500 or so requests.
Not super essential and I’m sure the Cursor team have more pressing priorities, but if it’s an easy win it’d be great to see!
hmm, that makes sense. an on/off switch would be nice.
Another discussion about this https://forum.cursor.com/t/toggle-between-fast-and-slow-requests/47756/4. Explains some likely rationale why this may not be prioritised. Kind of understandable. Would likely make ‘slow’ requests even slower. Would be interesting to get one of the Cursor team’s comment on this though!