I started a new conversation with an agent to do some rebase work, and after it finished only I noticed that Grok High is selected. I didn’t select it myself, as I’m usually either on Composer 2.5 or on Auto. This will mess up my budget for the rest of the month, and it’s really unacceptable.
Steps to Reproduce
Started a new conversation with a simple task, found out that the model selected is not what I usually select. Grok High was selected, and I’m usually either on Auto or Composer 2.5.
Hey, thanks for the report. This is a known issue in the current wave. In a new chat, the model can switch to Grok 4.5 by itself even if the user didn’t pick it. This is on our side, and I’ve filed it internally. I can’t share an ETA yet, but I’ll post an update in the thread once I have one.
Workaround for now: before starting a task in a new chat, check the model pill and manually switch it back to Auto or Composer 2.5. The switch happens when a new chat opens, so a quick model check before you start helps avoid unwanted usage.
About the charge for an unrequested model, it’s best to contact the team directly at [email protected]. They can review charges for your account.
Let me know if you see it switch again after you manually set the model back.