[BUG] VS Code extension continues consuming extra usage balance after session window reset instead of switching back to included plan usage

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

After my 5-hour session window reset (new window started at 0% usage), the Claude Code VS Code extension did not switch back to the included plan usage. Instead, it continued consuming my extra usage balance as if the previous exhausted session were still active.
When I disabled extra usage to force it to use the included allocation, I was completely blocked — unable to use Claude Code despite the new session window showing 0% consumption.

What Should Happen?

Expected Behavior:
On each new 5-hour session window, the extension should consume the plan's included usage first. Extra usage should only activate after the included allocation is exhausted within that window.
Actual Behavior:
The extension continued debiting from the extra usage balance immediately after the session reset, ignoring the newly available included usage. Disabling extra usage results in a full block with 0% of the new session consumed.

Error Messages/Logs

Steps to Reproduce

Exhaust the included usage of a 5-hour session window (extra usage activates)
Wait for the session window to reset
Observe that the extension continues consuming extra usage instead of the newly reset included allocation
Disable extra usage — access is fully blocked despite 0% consumption in the new window

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.98 VSCode Extension

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

About 100US$ or more used wrong.