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
With the appropriate setting enabled, gemini is supposed to switch to gemini-3-flash-preview after the plan is confirmed, but it doesnt, unless the immediate post plan actions are interrupted and a new message is sent.
What did you expect to happen?
A switch to gemini-3-flash-preview directly after the exit plan mode tool is run.
Hi can you run /stats model after creating and executing a plan. Also, set the model to Auto (Gemini 3). With automatic model switching enabled, we should expect to see Gemini 3.1 Pro and Flash being used.
Nope, I didnt change anything In between.
In the example you gave the agent explicitely didnt continue on due to the nature of the plan request, however if there is code involved it directly keeps going through with the implementation with gemini-3.1-pro. If I stop it and send continue, it then switches to gemini-3-flash, but this is more of a workaround.
It starts by showing Responding with gemini-3.1-pro-preview right when the initial message is sent. It then shows Responding with gemini-3-flash-preview only when the next message is sent, after it has exited plan mode and immediately implemented. It alligns with the above behavior.
But the issue is that is exits plan mode, starts implementing normally and only switches model after it is interrupted or stops and a new message is sent. In the example I had given above, it wrote the full html with gemini-3.1-pro. I would assume the expected behavior is a switch right after the plan is confirmed, not after it has written code. What I have to do now to not get it to consume 3.1 Pro tokens, is accept the plan, immediately ctrl + c and then send continue as a new message.
Activity
gemini-cli commentedon Mar 20, 2026
Found possible duplicate issues:
If you believe this is not a duplicate, please remove the
status/possible-duplicatelabel.Adib234 commentedon Mar 23, 2026
Hi can you run
/stats modelafter creating and executing a plan. Also, set the model toAuto (Gemini 3). With automatic model switching enabled, we should expect to see Gemini 3.1 Pro and Flash being used.TheTk58 commentedon Mar 23, 2026
I did and I can confirm it doesnt switch until I resend a message.
https://github.com/user-attachments/files/26195847/test.txt
Adib234 commentedon Mar 24, 2026
Hmm, did you switch to auto mid-session in plan mode? I tried reproducing the issue and couldn't when I start Gemini CLI with model
Auto (Gemini 3)However I can reproduce your issue when I have a model set at the beginning of my session and switch to auto in a random turn.
jerop commentedon Mar 24, 2026
fyi you can enabled
Show Model Info In Chatin/settingsto see which model is used in each turn:TheTk58 commentedon Mar 24, 2026
Nope, I didnt change anything In between.
In the example you gave the agent explicitely didnt continue on due to the nature of the plan request, however if there is code involved it directly keeps going through with the implementation with gemini-3.1-pro. If I stop it and send continue, it then switches to gemini-3-flash, but this is more of a workaround.
Adib234 commentedon Mar 24, 2026
Does using
Show Model Info In Chatshow that in the turns after you exited plan mode, pro model was being used?TheTk58 commentedon Mar 24, 2026
It starts by showing Responding with gemini-3.1-pro-preview right when the initial message is sent. It then shows Responding with gemini-3-flash-preview only when the next message is sent, after it has exited plan mode and immediately implemented. It alligns with the above behavior.
Adib234 commentedon Mar 24, 2026
I see, so in plan mode it was in gemini 3.1 pro and execution mode it was in flash? If so, this is expected behavior
TheTk58 commentedon Mar 24, 2026
But the issue is that is exits plan mode, starts implementing normally and only switches model after it is interrupted or stops and a new message is sent. In the example I had given above, it wrote the full html with gemini-3.1-pro. I would assume the expected behavior is a switch right after the plan is confirmed, not after it has written code. What I have to do now to not get it to consume 3.1 Pro tokens, is accept the plan, immediately ctrl + c and then send continue as a new message.