[BUG] 5-hour limit triggers just by launching the CLI (zero messages sent)?

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?

Hey everyone 👋, I've noticed a frustrating behavior with Claude Code and wanted to see if anyone else is dealing with this or has a workaround.

Whenever I launch claude in my terminal, the 5-hour usage limit timer seems to activate immediately, even before I type or send a single prompt. (And yes, this happens even when my quota is completely fresh and I haven't touched the web UI).

Has anyone figured out a way to prevent this? Is there a flag or setting to launch the CLI completely "blank" so it doesn't eat into the quota/start the timer until I actually hit enter on my first prompt?

Any insights would be super helpful. Thanks!

<img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/0c7d690d-5d31-41b7-814d-b828e2abef41" />
<img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/87a08952-b46c-43a2-af64-5b947bad240b" />
<img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/3797087a-db6b-478a-a94a-9a0944e0e5b1" />

What Should Happen?

It is supposed to only trigger countdown when a message is sent.

Error Messages/Logs

Steps to Reproduce

1. Have the 5h limit reset
2. Open claude code in a project
3. Limit countdown is triggered

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.143 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_