When you have reach a usage limit and is asked to switch to auto mode using the “switch to auto” button makes the dropdown value “auto” instead of “Auto”. This results in an error stating something like “there is no model named ‘auto’”
Steps to Reproduce
Reach the limit of some model or mode and click “switch to auto” button when prompted. Try to send another message to cursor.
Expected Behavior
It should make the model dropdown value “Auto” instead of “auto”
When a model’s rate limit or quota is exceeded, Cursor displays a “Switch to Auto” option. Upon accepting it, the model is changed to the raw string value “auto” (lowercase). However, when sending a new message afterwards, the request fails with: “Invalid model option: auto”. The workaround is to manually open the model picker dropdown and click “Auto”, which properly sets the model to the correct internal identifier.
Steps to Reproduce
Use a specific model (e.g., GPT-4.1) until its quota/rate limit is reached
When the “Switch to Auto” suggestion appears, accept it
Observe the model picker now shows “auto” (set programmatically)
Try sending a new message
Error appears: “Invalid model option: auto”
Manually click the model picker and select “Auto” — this works correctly
Expected Behavior
Accepting “Switch to Auto” should set the model to the same valid identifier as manually selecting “Auto” from the model picker dropdown, allowing requests to proceed without errors.
For AI issues: add Request ID with privacy disabled
Any model that hits its rate limit (e.g., GPT-4.1). The issue is with the “Switch to Auto” fallback mechanism.
Additional Information
The root cause appears to be that the programmatic “Switch to Auto” sets the model to the string “auto” instead of the proper model identifier (e.g., “copilot/auto” with vendor metadata). Manually selecting “Auto” from the picker works because it uses the full model object with correct identifier and metadata.
Model name is not valid: "auto" when switching model
Steps to Reproduce
When reaching you payment limit you can click “switch to auto” however this switches the model to “auto” only small letters causing the next submit to cause the following error:
This has bugged me enough to look for an answer here.
known bug or not, I am guessing the fix is small enough for you to get it fixed within a few minutes using cursor ;p
Don’t wait for Elon to buy Cursor. The small things like that will always please paid users
Hey, this is a known bug and we’re tracking it, but I can’t share an exact timeline for the fix yet.
Until it’s fixed, the workaround is to not click Switch to Auto. Instead, manually select Auto from the model dropdown. That sets the correct identifier, so requests won’t fail with the error Model name is not valid: "auto".
Once I have an update on the fix, I’ll reply in this thread.
