# Changing model in message dropdown after a failed prompt does not apply the newly selected model **URL:** \ **Category:** Bug Reports\ **Tags:** chat\ **Created:** [October 26, 2026, 9:23pm UTC](https://forum.cursor.com/t/changing-model-in-message-dropdown-after-a-failed-prompt-does-not-apply-the-newly-selected-model/176284 "2026-10-26T21:23:46Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![joeybab3](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/joeybab3/32/102269_2.png) [@joeybab3](https://forum.cursor.com/u/joeybab3)\ **Post date:** [October 26, 2026, 9:23pm UTC](https://forum.cursor.com/t/changing-model-in-message-dropdown-after-a-failed-prompt-does-not-apply-the-newly-selected-model/176284/1 "2026-10-26T21:23:46Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug Changing model in the previously sent message dropdown after a failed prompt does not apply the newly selected model ### Steps to Reproduce 1. ask grok 4.7 anything 2. cursor claims its not in the registry (unrelated issue) 3. change the model to one that we know works 4. sending a message fails for the same issue around the old model ### Expected Behavior I’m fine with 4.7 not working because that model is not great but the dropdown should change the model. this is also relevant when there are outages on certain models. the dropdown in the chat all the way at the bottom does work, if i change it there and press submit in the chat message its fine. ### Screenshots / Screen Recordings ### Operating System MacOS ### Version Information Version: 3.27.12 (Universal) VS Code Extension API: 1.128.0 Commit: df132ffba90dfc15a12e6b8f020ba4e5d026c4b0 Date: 2026-10-23T02:27:47.076Z Layout: IDE Build Type: Stable Release Track: Default Electron: 42.11.16 Chromium: 148.0.7778.280 Node.js: 24.19.0 V8: 14.8.178.38-electron.0 xterm.js: 6.1.0-beta.291 OS: Darwin arm64 25.6.0 ### For AI issues: which model did you use? grok 4.7 ### Additional Information highlighting is not visible in whatever color scheme i have it in for some reason, cant tell when you are highlighting text in a previously sent message ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [October 27, 2026, 9:16am UTC](https://forum.cursor.com/t/changing-model-in-message-dropdown-after-a-failed-prompt-does-not-apply-the-newly-selected-model/176284/8 "2026-10-27T09:16:42Z")
Hi @joeybab3, the model picker on an edited message isn’t being applied in the IDE layout right now. The resend still goes out with the model set on the chat itself, which is why it kept failing on Grok 4.7. I’ve passed this to the team. In the meantime, change the model in the dropdown under the chat input at the bottom (as you found), then resend or edit the message. That dropdown updates the chat’s model, so the resend picks it up. The Grok 4.7 error looks like it may be tied to the 500K context option being selected while Max Mode is off. Opening Grok 4.7’s options and setting Context to 256K (or turning on Max Mode) should get it running again. On the highlighting, could you raise a seperate thread with more information? ---
**Author:** ![joeybab3](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/joeybab3/32/102269_2.png) [@joeybab3](https://forum.cursor.com/u/joeybab3)\ **Post date:** [October 27, 2026, 9:12pm UTC](https://forum.cursor.com/t/changing-model-in-message-dropdown-after-a-failed-prompt-does-not-apply-the-newly-selected-model/176284/10 "2026-10-27T21:12:17Z")
Yes to all, worth noting I never set the context to 500k tokens, that seems the be the default when trying to switch models? regardless an error message stating that it is due to the context length would probably be a better experience then the error message. Why is 500k even selectable if it requires another setting to be enabled? I would say if this is something that requires max mode have it be shown but greyed out, and certainly should not be able to become the default. ![Screenshot 2026-10-27 at 2.09.08 PM](https://us1.discourse-cdn.com/cursor1/original/3X/d/f/df63960dd3830836f8a098b994d794d70e8ad6a1.png) ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [October 28, 2026, 11:19am UTC](https://forum.cursor.com/t/changing-model-in-message-dropdown-after-a-failed-prompt-does-not-apply-the-newly-selected-model/176284/22 "2026-10-28T11:19:54Z")
Hi @joeybab3, you shouldn’t need to do anything more. Setting Context to 256K for Grok 4.7 in the picker under the chat input replaces the 500K that had been saved for it, so since that worked for you the old value is gone. If it ever comes back: 1. Open the model picker under the chat input, hover Grok 4.7 and click the reset arrow (or Restore defaults in its options, depending on your version). That clears its saved settings and goes back to the default, 256K. 2. Older chats remember their own model settings, so if one of them still fails, pick the Context again in that chat before sending. On your plan, 500K doesn’t need a separate Max Mode setting, so picking it fresh should work. The failures came from an older 500K choice being sent without the setting that goes with it.