You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
enhancementRequested improvement or new capability.needs-triageIssue needs maintainer review and initial categorization.
2 participants
Converted from issue
This discussion was converted from issue #5259 on August 15, 2026 09:47.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/desktop
Problem or use case
Cursor recently announced a cursor router, see https://cursor.com/changelog/router.
In the agent CLI, it is present:
But in the T3 code nightly, there are two auto modes showing up without a clear difference:
Proposed solution
In the model selection, either all 3 auto mode (route) based models are present or allow to choose further in the same auto mode model.
Why this matters
Cursor auto mode default is balanced (assumed based on the model selection) which uses sol model and consumes a lot of credits.
So it would be helpful to run it on Cost optimized.
Smallest useful scope
Just model selection option for cursor's agent cli.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution
All reactions