[BUG] --resume causes massive silent token drain on session restore (Pro, v2.1.193)

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?

When launching Claude Code via a desktop shortcut using --resume <session-id>, the 5-hour usage window is exhausted within approximately 1 hour of light work. The same workload the previous day (without --resume) did not trigger early exhaustion. The session from the previous day is fully reprocessed silently on launch, consuming a large amount of tokens before the user types a single message.

What Should Happen?

Resuming a session with --resume should not reprocess the entire prior conversation context on launch. The prompt cache from the previous session should be reused where possible, so that the token cost on resume is negligible — not equivalent to replaying the full prior session from scratch. Users should not be charged twice for the same tokens.

Error Messages/Logs

Steps to Reproduce

● API Error: Request rejected (429) · [1308][Usage limit reached for 5 hour. Your limit will reset at 2026-06-27 06:44:00][20260627025404544a4e1524834c14]

✻ Worked for 3m 17s

❯ avabo de empezar... no han pasado las 5 horas!!

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.193 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_