[BUG] [New Version Issue: v2.1.270] Random Session Expiry with reset time >5 hours beyond current time.

Status Open
Reported on v2.1.270
Maintainer reply None cached
Activity 3 comments · opened Sep 13, 2026

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?

Claude suddenly reset my 5hr window by suggesting limit used but the return time was set for almost 6 hrs from the time the reset was applied.

This is very strange because, my then current session had 1 hr remaining to session reset. This made me wait 6 hours (from the time of reset).

What Should Happen?

Session should only restrict you from the sliding window of the session not 5hrs from the time when claude perceived the 5h session limit is reached.

Error Messages/Logs

Steps to Reproduce

  1. Use claude code normally
  2. Burn tokens upto for 4 hrs with 1 hr remaining for the 5hr window.
  3. Burn up to 100%
  4. Usage restricted for 5hrs from the time it hit 100% not 1 hr because 100% is reached at 4th hr of the session.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.270

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

3 Comments

saikat-crux · 23 hours ago

<img width="429" height="263" alt="Image" src="https://github.com/user-attachments/assets/7cf54811-338d-4e68-a353-3b676b40f50f" />

Folks please roll back you prompt cache and cache invalidation feature, I am pretty sure this is the culprit it is burning tokens like crazy went from 17% to 99% in under 30mins with Sonnet on Medium effort. This is unreasonable.

saikat-crux · 22 hours ago

I am super frustrated at this point, it burned through the 30% of weekly limit doing the same things it did by burning through 4% of the limit. There is definitely something goofy going on. Either the scheduleWait is not working or Cache invalidation is getting messed up. On this new version I see cache invalidation time as a new feature and getting automatically set to 60mins and then decrementing and then going back to 60 mins in about 10-15mins. (I am not sure if that is causing this issue)

saikat-crux · 22 hours ago

This is when the issue started:

<img width="192" height="185" alt="Image" src="https://github.com/user-attachments/assets/abf49c2b-75a1-4d5b-84bf-edf4022166f7" />