I use a Cursor Project Orchestrator, and initially I started it with a 4.7 high model, but then I have switched it in the model picker to 4.6 high. It keeps defaulting to 4.7 high. It absolutely ignores what I have set.
In settings, in Agent > Conversation> Model, I have selected “last used” instead of “cursor default”, and I still face this issue.
Steps to Reproduce
Start the projects orchestrator with a 4.7 high model. Send a few messages, and then in the model picker, switch to 4.6 high and send another message. Notice that this is still built as a 4.7 high model.
Hey @jmokut, thanks for the report and the screenshot.
We looked into this Project. The switch back to Grok 4.7 High lines up with messages your Grok Bot sent to the Project: when Grok Bot messages a cloud agent it can also set that agent’s model, and here it set Grok 4.7 High, which then stuck for every following turn. Messages you send from the Project window keep the agent’s current model unless the picker selection actually changes, and in your case the picker was still showing Grok 4.6 High from before, so nothing was sent to switch it back.
To get it back on Grok 4.6 High, could you try:
Open the Project in the Agents window.
Click the model picker and choose any other model.
Click the model picker again and choose Grok 4.6 High.
Send a message, then ask the agent which model it is running.
If Grok Bot is also messaging this Project, ask Grok Bot to keep the Project on Grok 4.6 High (or to not set a model when it messages the Project), otherwise its next message may switch it again.
Let us know whether it stays on Grok 4.6 High after that. I’ve passed this to the team as well.
FWIW, This feels wrong as a silent failure - I’d never have realized the project coordinator was running on a different model if I didn’t look at my usages on my billing dashboard. If for whatever reason the model changed, I’d expect the model picker to reflect this change.
