Gotta select auto agent at every run

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

(pro - not team account) used to be able to set Auto and it doesn’t require me to keep changing the model at every chat/prompt. now it’s frustratingly asking me to set auto but auto doesn’t exist is the error.

Steps to Reproduce

run a prompt click submit and says you’ve run out of limits. choose auto

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.6.31 (Universal)

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This is a known bug. The switch to auto button that shows up after you hit the limit sets the model to auto lowercase instead of Auto, so you get the model doesn’t exist error.

Workaround for now: don’t click switch to auto. Instead, manually pick Auto from the model dropdown in the chat. That will save correctly and you won’t see the error.

We’ve logged the bug, but I can’t share an ETA yet. I’ll post an update in the thread when I have one.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I get the message that my token pool is empty, I get a button that says “swtich to auto” and when I click it it tries to select “auto” with lowercase while I suspect that it should select “Auto” with uppercase “A”. However it doesnt select the correct model and fails once again with the message ‘invalid model “auto”’

Steps to Reproduce

Run out of tokens and then click “switch to auto” that automatically pops up.

Expected Behavior

It should select the correct Auto mode.

Operating System

Windows 10/11

Version Information

Version: 3.6.31 (user setup)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer 2.5 Fast

Does this stop you from using Cursor

No - Cursor works, but with this issue

the workaround works sometimes. it takes about like 100 times (per chat window) before it learns that I have chosen auto and follows through.

Hey Jenny, thanks for coming back with details. Auto not sticking the first time sounds like the same limit-retry flow that’s breaking the button. Even with manual selection it sometimes falls back.

To narrow this down, can you help with two things?

  1. When it fails, is it that selecting Auto from the dropdown throws an error, or does Auto get set but then it resets again on the next prompt?
  2. Please share a Request ID from one of the failed attempts: chat menu in the top right > Copy Request ID.

I’ve already reported the bug, no ETA on a fix yet. I’ll post an update in the thread as soon as I have one.