Hey, thanks for the report. This is a known issue affecting Auto mode right now. We’ve seen multiple reports from different users since this morning.
Workaround: instead of Auto, pick a specific model (for example, Sonnet 4.5 or GPT 5). That should work fine. You can switch the model in the dropdown menu in the chat.
The team is already working on a fix.
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Hi everyone,
I’m running into an issue with Cursor and wanted to check if anyone else is experiencing the same problem.
Cursor was working normally for me earlier this morning. However, starting around 1:30 AM (Taiwan time, GMT+8), my IDE began repeatedly showing the following error message:
“the model default does not work with your current plan or API key”
Since then, I haven’t been able to use Cursor properly because this message keeps popping up.
I haven’t changed:
my subscription plan
my API key
any related settings
So I’m wondering:
Did something change on Cursor’s side?
Is there a temporary outage or model availability change?
Has the default model behavior or plan requirement been updated?
Any clarification or guidance would be greatly appreciated.
Thanks in advance!
Steps to Reproduce
ok
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.3.41 (Universal)
Does this stop you from using Cursor
Yes - Cursor is unusable
Just to confirm, switching to Sonnet 4.5 or GPT-5 won’t incur any additional costs, correct?
I’ve already hit the usage limit so I cannot use other model…
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Hi everyone,
I’m running into an issue with Cursor and wanted to check if anyone else is experiencing the same problem.
Cursor was working normally for me earlier this morning. However, starting around 1:30 AM (Taiwan time, GMT+8), my IDE began repeatedly showing the following error message:
“the model default does not work with your current plan or API key”
Since then, I haven’t been able to use Cursor properly because this message keeps popping up.
I haven’t changed:
my subscription plan
my API key
any related settings
So I’m wondering:
Did something change on Cursor’s side?
Is there a temporary outage or model availability change?
Has the default model behavior or plan requirement been updated?
Any clarification or guidance would be greatly appreciated.
Thanks in advance!
Steps to Reproduce
ok
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.3.41 (Universal)
Does this stop you from using Cursor
Yes - Cursor is unusable
The Same!
currently having this issue with auto but selecting a model works
Same issue here with plan builds
Having the same issue under these params.
Version: 2.3.41 (system setup)
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
Same
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I keep getting the following error when starting a prompt “The model default does not work with your current plan or api key” for any request. I am well within my subscription limits.
Steps to Reproduce
Opening Cursor and starting any prompt is blocked.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Does this stop you from using Cursor
Yes - Cursor is unusable
Hey everyone, can you share the Request ID for this case? The team is investigating an issue with Auto mode.
How to get your Request ID:
- Open the chat context menu (three dots in the top right)
- Select “Copy Request ID”
This’ll help our engineers figure out what’s going on with Auto mode.
bbdad55b-d33c-4151-bb23-53eb69e5a541
5dd1c789-5142-4f64-b6b6-51a34d6bb3f7
it seems like auto mode is back.
we got the same unavailable msg notification from Cursor IDE around 1 hour ago.
FYI
Mine was back for a little while, but now it’s broken again.
49bac3d0-a68c-47eb-b23a-b2474f4ee1ca




