Model switching may still charge the earlier model’s usage
In , using Sonnet to create a plan and then switching to Gemini to carry out the changes worked well overall. The problem is that Sonnet usage appeared to keep going down even after the model was switched to Gemini. More detailed real-time usage tracking made this easier to notice.
Common explanations include hidden , multiple sessions, or other , but this case used skills inside the IDE with no . After starting a normal workflow and creating an , the model switch still seemed to leave Sonnet usage being deducted, making the usage calculation unclear.
Key points
- Sonnet was used for planning, then Gemini was used for execution.
- Sonnet usage appeared to keep being deducted after switching to Gemini.
- The case did not involve or multiple sessions.
- Real-time usage tracking helped reveal the possible mismatch.
- Cost-saving need direct checks of how each model’s usage is counted.