# Cursor is unusable with own api key since update

**URL:** <https://forum.cursor.com/t/cursor-is-unusable-with-own-api-key-since-update/53746>\
**Category:** Bug Reports\
**Created:** [February 24, 2025, 6:52am UTC](https://forum.cursor.com/t/cursor-is-unusable-with-own-api-key-since-update/53746 "2025-02-24T06:52:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![SkySlider](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/skyslider/32/28841_2.png) [@SkySlider](https://forum.cursor.com/u/SkySlider)\
**Post date:** [February 24, 2025, 6:52am UTC](https://forum.cursor.com/t/cursor-is-unusable-with-own-api-key-since-update/53746/1 "2025-02-24T06:52:51Z")

</div>

![image](https://us1.discourse-cdn.com/cursor1/original/3X/4/3/43bc4fd3c897002a102c082eb5ac686c876c7355.png)  
After update, you have to choose a mode for interacting - Agent, Ask, Edit. No matter what I pick I get the same error.

So, I guess devs are dropping everyone using api key? Quite greedy for vscode fork.  
I’m not paying 20$ for measly 500 requests, I use that amount in couple of days. I don’t need any fancy shmancy composers/agents all that bs.

What are other options out there, besides cline?

---

<div class="post-metadata">

**Author:** ![VIRUXE](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/viruxe/32/23883_2.png) [@VIRUXE](https://forum.cursor.com/u/VIRUXE)\
**Post date:** [February 24, 2025, 10:45am UTC](https://forum.cursor.com/t/cursor-is-unusable-with-own-api-key-since-update/53746/3 "2025-02-24T10:45:03Z")

</div>

You get 500 “fast” requests. After that amount, they are just slower.

Plus, you get many more requests out of a subscription than just using the API key. And more features.

Also, there are a lot of small edits that can be done using gpt4o-mini which is free, to save fast credits. Or even using Haiku and o3-mini that count 1/3 of a fast request.

![Screenshot 2025-02-24 111245](https://us1.discourse-cdn.com/cursor1/original/3X/5/c/5cd060bbfb302b9b31a27b39bc6e8e7783aaba1e.png)

And slow requests are just fine. If you prompt Sonnet it’s almost like prompting o1 in terms of wait time.

---

<div class="post-metadata">

**Author:** ![SkySlider](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/skyslider/32/28841_2.png) [@SkySlider](https://forum.cursor.com/u/SkySlider)\
**Post date:** [February 24, 2025, 11:22am UTC](https://forum.cursor.com/t/cursor-is-unusable-with-own-api-key-since-update/53746/4 "2025-02-24T11:22:25Z")

</div>

I know all about that, but I don’t really need any of it. Price isn’t the issue here; it’s the fact that you could use your API key, which hasn’t been possible since the last update.

---

<div class="post-metadata">

**Author:** ![jcgentr](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jcgentr/32/29150_2.png) [@jcgentr](https://forum.cursor.com/u/jcgentr)\
**Post date:** [February 24, 2025, 9:05pm UTC](https://forum.cursor.com/t/cursor-is-unusable-with-own-api-key-since-update/53746/5 "2025-02-24T21:05:26Z")

</div>

As a user that has only ever used their own API keys, this is so frustrating. I shouldn’t be forced into another AI subscription. Feels like a rug pull. At least grandfather those of us in that have used the product for awhile with our own API keys.

Also, seems strange that I can use the API key in quick edit mode but not edit mode in the chat window.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [March 26, 2025, 9:05pm UTC](https://forum.cursor.com/t/cursor-is-unusable-with-own-api-key-since-update/53746/6 "2025-03-26T21:05:58Z")

</div>

Closed on March 26, 2025, 9:05pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
