[BUG] Session limit hits 100% despite minimal usage and low token consumption

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?

The "Current session" limit (short-term rate limit) consistently shows 100% used and prevents further usage, despite minimal activity and very low token consumption in the current session. The weekly limit is only partially used (30%), confirming the issue is specific to the session-level metering.

When running /usage, the session shows:

Total cost: $0.0000

Total duration (API): 0s

Total duration (wall): 3s

Usage: 0 input, 0 output, 0 cache read, 0 cache write

Yet the "Current session" bar shows 100% used and will not reset until the daily rollover.

What Should Happen?

The session limit should reflect actual usage. With 0 input/output tokens and only a few messages, the session meter should show low usage (e.g., <10%), not 100%. A session should reset based on actual consumption, not exhaust after minimal prompts.

Error Messages/Logs

Steps to Reproduce

Start a new Claude Code session.

Use /clear between tasks to keep context short.

Send only a few messages (in my case, only 1-2 moderate prompts).

Run /usage and observe the "Current session" limit at or near 100%.

Attempt to continue using Claude Code and receive a "limit finished for the session" error.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.239

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_