Model choice not saving on edit queued task

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Changing the model that should be used on a queued prompt is not actually changing it when it has been changed in the UI and re-entered.

Also, users need to be able to set preferred or default models.

Steps to Reproduce

Set multiple tasks, go in to change the model for one, enter, check again, model is not changed

Expected Behavior

Model for task should change when changed.

Operating System

Windows 10/11

Version Information

Version: 3.19.13 (user setup)
VS Code Extension API: 1.128.0
Commit: dd066f332fcea7382764400fde902f61920648d0
Date: 2026-09-04T17:41:16.065Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Hey there, thanks for the clear report! You’ve got this right. In the Agent Window, editing a message that’s already queued and changing the model doesn’t stick. The row keeps the model it was originally queued with, so reopening the edit shows the old one. That’s not intended behavior, and it’s nothing on your end. We’ve let the team know and it’s an issue we’re tracking.

Quick workaround: instead of editing the queued message, remove it (the X on the row), pick the model you want, then retype it and press Enter to queue it fresh. A newly queued message does keep whatever model was selected when you pressed Enter.

On preferred/default models: the picker already remembers your last choice for new chats, and I’ve passed along the request for a per-task default too. I’ll follow up here if there’s an update.