You've hit your session limit · resets 5pm (Europe/Paris)

Bug Description
Issue: Idle Claude Code Terminal CLI sessions consume excessive usage via cached token reads without active user input
Steps to reproduce:
Open a Claude Code Terminal CLI session
Leave the session open for an extended period (e.g., 24+ hours) without actively sending messages
Run /usage to check consumption
Product/Surface: Claude Code Terminal CLI
Details:
Session remained open for 1 day 3 hours 38 minutes (wall time) with only 1h 49m of active API usage
100% of usage occurred at >150k context
$107.22 cost primarily from 184.3 million cache read tokens
Session hit 100% usage limit despite no new messages being sent
User unable to work due to exhausted session limit
Expected behavior: Idle sessions should not consume significant usage when no active messages are being sent.
I mean why am I paying 100 dollars a month to arrive to my session limit without typing any message (literally none). Continuously. For 24 hours x) nearly 5 sessions.

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.220
• Feedback ID: bd9d0ad8-ba8a-42ec-8777-8d4d7945943b

Errors

[]