# What exactly are fast requests?

**URL:** <https://forum.cursor.com/t/what-exactly-are-fast-requests/46>\
**Category:** Discussions\
**Created:** [August 23, 2023, 7:12am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46 "2023-08-23T07:12:34Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![pmz](https://avatars.discourse-cdn.com/v4/letter/p/f4b2a3/32.png) [@pmz](https://forum.cursor.com/u/pmz)\
**Post date:** [August 23, 2023, 7:12am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/1 "2023-08-23T07:12:34Z")

</div>

I’m loving Cursor.  
Though I don’t understand what “fast” requests are?

I see that there are only 500 per month, which obviously won’t be enough.  
What happened after that?

How can one “save” fast requests and use regular gpt4 requests?

---

<div class="post-metadata">

**Author:** ![truell20](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/truell20/32/28583_2.png) [@truell20](https://forum.cursor.com/u/truell20)\
**Post date:** [August 23, 2023, 7:30am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/2 "2023-08-23T07:30:23Z")

</div>

Fast requests get first priority on our backend. Slow requests will be queued behind fast requests in times of particularly high load. Otherwise, they’ll run the same speed.

---

<div class="post-metadata">

**Author:** ![siraj](https://avatars.discourse-cdn.com/v4/letter/s/a9adbd/32.png) [@siraj](https://forum.cursor.com/u/siraj)\
**Post date:** [August 30, 2023, 4:25am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/3 "2023-08-30T04:25:05Z")

</div>

Thanks for clarifying - is there any way to save fast for the times that we feel is critical for us, when we think that we might need fast responses.

---

<div class="post-metadata">

**Author:** ![martinopensky](https://avatars.discourse-cdn.com/v4/letter/m/3be4f8/32.png) [@martinopensky](https://forum.cursor.com/u/martinopensky)\
**Post date:** [August 30, 2023, 11:17am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/4 "2023-08-30T11:17:10Z")

</div>

Yeah, when creating code using Command + K, it’d be helpful to have an option to toggle fast or slow…similar to when you have the option to toggle between gpt-3.5 and gpt-4 using the chat

---

<div class="post-metadata">

**Author:** ![RealityMoez](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/realitymoez/32/84351_2.png) [@RealityMoez](https://forum.cursor.com/u/RealityMoez)\
**Post date:** [August 30, 2023, 7:14pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/5 "2023-08-30T19:14:37Z")

</div>

it’s already there. I don’t know when, but it appeared couple of times for me.  
_(I think it appears if you have gpt-4 fast requests available)_

> [@martinopensky](#):
>
> when creating code using Command + K, it’d be helpful to have an option to toggle fast or slow

---

<div class="post-metadata">

**Author:** ![martinopensky](https://avatars.discourse-cdn.com/v4/letter/m/3be4f8/32.png) [@martinopensky](https://forum.cursor.com/u/martinopensky)\
**Post date:** [August 31, 2023, 6:30pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/6 "2023-08-31T18:30:17Z")

</div>

After taking a look at this again, I realised that the setting gpt-3.5 or gpt-4 on the Chat works for all commands not just the chat

---

<div class="post-metadata">

**Author:** ![martinopensky](https://avatars.discourse-cdn.com/v4/letter/m/3be4f8/32.png) [@martinopensky](https://forum.cursor.com/u/martinopensky)\
**Post date:** [September 1, 2023, 2:49pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/7 "2023-09-01T14:49:35Z")

</div>

Hey @truell20,  
I’m now using Pro for the first time and loving the experience!

Is there a way to toggle between gpt-4 fast and slow queries? It’d be nice to have an extra option for the Pro subscription next to the usual gpt-3.5 and gpt-4 i.e. gbt-4-fast

![Xnapper-2023-09-01-15.48.18](https://us1.discourse-cdn.com/cursor1/original/1X/1cb9bda3a56cdfb14af4f5f1db7ce5dd9b562bf3.png)

This way I can choose when I need to use up my 500 per month fast queries

---

<div class="post-metadata">

**Author:** ![unity\_gamedev](https://avatars.discourse-cdn.com/v4/letter/u/977dab/32.png) [@unity\_gamedev](https://forum.cursor.com/u/unity_gamedev)\
**Post date:** [September 1, 2023, 5:55pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/8 "2023-09-01T17:55:31Z")

</div>

Maybe the name should be more like “priority” rather than fast, since fastness as a concept is probably already hogged by gpt 3.5 vs gpt 4.

Plus, if there are no prioritized tasks in the queue, a non-prioritized task will not be slower, if I understand right

---

<div class="post-metadata">

**Author:** ![amanrs](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/amanrs/32/105_2.png) [@amanrs](https://forum.cursor.com/u/amanrs)\
**Post date:** [September 1, 2023, 9:22pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/9 "2023-09-01T21:22:20Z")

</div>

We don’t currently have a way for users to toggle between slow/queued requests and fast/priority requests. This seem to be a decent number of requests for this, so we will likely will add it in a future release

---

<div class="post-metadata">

**Author:** ![GhostKiller](https://avatars.discourse-cdn.com/v4/letter/g/a9a28c/32.png) [@GhostKiller](https://forum.cursor.com/u/GhostKiller)\
**Post date:** [September 5, 2023, 7:47pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/10 "2023-09-05T19:47:08Z")

</div>

I second this feature and would also like it to be called priority queue/request rather than slow vs fast.

Thx ^^

---

<div class="post-metadata">

**Author:** ![leoing](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leoing](https://forum.cursor.com/u/leoing)\
**Post date:** [December 6, 2023, 9:12am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/11 "2023-12-06T09:12:19Z")

</div>

I’d also like to be able to toggle between priority and normal requests.

Also, I would like to be able buy extra fast/priority requests. It seems not to be possible (or is hidden in business somewhere?)?

---

<div class="post-metadata">

**Author:** ![jsindos](https://avatars.discourse-cdn.com/v4/letter/j/46a35a/32.png) [@jsindos](https://forum.cursor.com/u/jsindos)\
**Post date:** [January 6, 2024, 8:07am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/12 "2024-01-06T08:07:38Z")

</div>

There is an option at cursor.sh/settings, however, I’m not sure how the top up works when close to the end of the month. Do the extra fast requests expire once the next month starts?

 ![image](https://us1.discourse-cdn.com/cursor1/original/1X/ebef8aba9efa83c0d1afe50ce1c913388d07fd79.png)

---

<div class="post-metadata">

**Author:** ![leoing](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leoing](https://forum.cursor.com/u/leoing)\
**Post date:** [January 6, 2024, 9:03am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/13 "2024-01-06T09:03:36Z")

</div>

You can now buy another 500 (or more) priorty requests. Hit’s me usually after half a month, so I just use that. Makes my monthly price $20+$20

---

<div class="post-metadata">

**Author:** ![mtf](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mtf/32/7788_2.png) [@mtf](https://forum.cursor.com/u/mtf)\
**Post date:** [January 8, 2024, 5:49pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/14 "2024-01-08T17:49:30Z")

</div>

+1 Any news on this? Would be really great to have this feature!

---

<div class="post-metadata">

**Author:** ![leoing](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leoing](https://forum.cursor.com/u/leoing)\
**Post date:** [January 12, 2024, 6:23pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/15 "2024-01-12T18:23:51Z")

</div>

It’s much less nice, than I thought, check out

> [@Accounting bug in pro, #fastAccess](https://forum.cursor.com/t/accounting-bug-in-pro-fastaccess/2405):
>
> Hi, I reached 500 fast access limit Dec 21st 2023. I bought 500 extra. Have just seen that this subscribes 2xPro - not good, wasn’t communicated. Used up 640 of my 1000 fast accesses. The remainder seems to decay Jan 18th? Also not good. So I changed it back to 1xPro for my next month. Now it shows “reached limit of 500 fast accesses” (for the remainder of my current month). Also not good. I think a good solution would be to be able to buy a number of extras - but this should not change the…

---

<div class="post-metadata">

**Author:** ![parisneto](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/parisneto/32/4551_2.png) [@parisneto](https://forum.cursor.com/u/parisneto)\
**Post date:** [September 10, 2024, 4:35pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/16 "2024-09-10T16:35:12Z")

</div>

Good to know, I am a fresh subscriber and believer of Cursor, Just today I used 10% of my fast requests without knowing, and I was not in a hurry with basic edits I used to make in GPT directly, I would love to save my fast requests for when I really needed, instead of burning them FiFO without need ! +1 for the option to toggle Fast/Not so Fast requests.

---

<div class="post-metadata">

**Author:** ![Reynau](https://avatars.discourse-cdn.com/v4/letter/r/d6d6ee/32.png) [@Reynau](https://forum.cursor.com/u/Reynau)\
**Post date:** [September 11, 2024, 2:55pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/17 "2024-09-11T14:55:45Z")

</div>

Yes, that feature would be greatly appreciated. Let’s see if they build it up

---

<div class="post-metadata">

**Author:** ![mwk24](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mwk24/32/7131_2.png) [@mwk24](https://forum.cursor.com/u/mwk24)\
**Post date:** [October 3, 2024, 9:41am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/18 "2024-10-03T09:41:37Z")

</div>

Yes. A quick fix would be to just add to the dropdown… GTP-4o (slow) etc. I don’t want to power through all my 500, sometimes I don’t mind slow if I’m doing something else.

---

<div class="post-metadata">

**Author:** ![parisneto](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/parisneto/32/4551_2.png) [@parisneto](https://forum.cursor.com/u/parisneto)\
**Post date:** [November 14, 2024, 5:36pm UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/19 "2024-11-14T17:36:21Z")

</div>

> [@mwk24](#):
>
> add to the dropdown… GTP-4o (slow) etc. I don’t want to power through all my 500, sometimes I don’t mind slow if I’m doing something else.

upvoted, to #Feature Requests great idea and totally agree !

while I understand slow requests can also be fast and that should have a deeper tie with business model and subscription costs, and I will skip that for a minute

For the user experience is really stressfull to see meaningless usage eating your precious and most of the times magical power of Cursor, this would also become a better way to educate users and tiered service level until world has more energy, money and GPUs.

---

<div class="post-metadata">

**Author:** ![grumegargler](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/grumegargler/32/36396_2.png) [@grumegargler](https://forum.cursor.com/u/grumegargler)\
**Post date:** [March 16, 2025, 6:46am UTC](https://forum.cursor.com/t/what-exactly-are-fast-requests/46/20 "2025-03-16T06:46:18Z")

</div>

Sorry for the probably obvious to everyone question, but I could not find information about what exactly Request is (fast or slow - doesn’t matter). Is there a clear answer to that? (the documentation doesn’t answer this question either)

[Next page](https://forum.cursor.com/t/what-exactly-are-fast-requests/46.md?page=2)
