[BUG] Claude start session with 100% 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 the weekend, I returned to work and noticed an issue with usage limits.

On May 4, immediately after asking the first question in a new session, the system indicated that I had already reached 100% of my usage limit.

On May 5, I waited until the usage limits were supposed to reset (after midday). I submitted a question and briefly saw around 900 tokens being used, after which my usage jumped to 40% almost instantly on the usage page.

This behavior seems inconsistent with normal usage and may indicate a problem with how limits are being calculated or displayed. Could you please investigate?

What Should Happen?

Based on my experience, even when using the most advanced models on complex tasks, the system typically takes longer to process the request but produces high-quality results while consuming no more than around 20% of my usage.

In contrast, in this case I observed that a very simple request (essentially just a greeting) on a lightweight model immediately consumed about 40% of my usage. This seems disproportionate and inconsistent with expected behavior.

Error Messages/Logs

Steps to Reproduce

Take a short break and then return to the task
Submit the first question

Observed Behavior

The system immediately reports a very high usage (up to 100%) after the first request, or shows a disproportionately large increase (e.g., ~40%) even for a simple query

Expected Behavior

Usage should reset correctly after the break/reset period
Simple queries should consume only a small portion of the available usage

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

4.7

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_