Gemini 2.5 flash 04-17 is too sticky on Gemini Code Assistant

I don’t know what the behind-the-scenes process is for informing the Code Assistant, but it is repeatedly replacing the newly released “gemini-2.5-flash” AND the “gemini-2.5-flash-lite-preview-06-17” with the “gemini-2.5-flash-preview-04-17” because its guidelines only mention “gemini 0417” as the fast and efficient model! So it replaces the other two with this “older” version of Gemini Flash because it is instructed to do so, even after Gemini 2.5 Flash was released as a “stable version”.

This has become quite annoying because if I start a new session with Gemini Code Assist and don’t specify that I want to use the stable Flash and Flash Lite models on the project, it just changes them back to the 04-17 model on its own. I even had an “Architecture.md” file on the project specifying and explaining how the 04-17 is an older model and that for my project I wanted to use the Gemini 2.5 Flash and the Flash Lite models. But the Code Assistant actually REWROTE the Architecture.md document, removing those instructions and just making every part of my project use “gemini-2.5-flash-preview-04-17” for every function instead!

I don’t know how difficult it is to update the code or just the documentation it uses as instructions for best practices, but it REALLY needs to change, because this is becoming unbearable. Every day I start a new session, I have to check if the Code Assist decided to just go rogue and change everything back to the old models because it thinks it is the best practice!

So yeah, anyone responsible for this, please tell me if that’s already in the plans to update it, or if this is already a known issue… Give me some assurance, please! Thanks!