Back to rankings

Claude Code Warns Before Resuming an Old Conversation Would Burn Your 5-Hour Limit

Claude CodeView original changelog

Claude Code v2.1.304 shows a warning on Pro and Max plans when resuming an inactive conversation would use a noticeable share of the 5-hour usage limit. Users can resume anyway, or start a new conversation and refer to the previous one, which Claude can look up. The change targets the hidden cost of reloading a long, cache-cold session.

Key Takeaways

  • The warning appears only on Pro and Max plans, where usage is metered against a rolling 5-hour limit.
  • It triggers when a resume would use a noticeable share of the 5-hour limit, not on every resume.
  • Users can resume anyway, so the warning informs rather than blocks.
  • The alternative is to start a new conversation, and Claude can look up the previous one when the user refers to it.
  • The underlying cost is the cache-cold re-read of the full history after a long idle gap.
  • The same release fixes 1-hour /loop wakeups firing just after the prompt cache expired, which re-read conversations uncached.

A warning before an expensive resume

Resuming a long conversation after a break can be costly. Once the prompt cache has expired, the whole history has to be read again at full price, and on subscription plans that cost comes out of the rolling 5-hour usage limit. Claude Code v2.1.304 adds a warning for exactly this case on Pro and Max plans.

When resuming an inactive conversation would use a noticeable share of the 5-hour limit, Claude Code now says so before it proceeds. The user then has two choices. They can resume anyway and accept the cost, or start a new conversation. In the new conversation, Claude can look up the previous one if the user refers to it, so earlier work is not lost.

Related caching fix in the same release

v2.1.304 also fixes self-paced /loop wakeups scheduled at the 1-hour maximum. They previously fired just after the 1-hour prompt cache expired, so each wakeup re-read the whole conversation uncached. That fix does not change the resume warning, but it comes from the same concern about avoidable uncached reads.

Why it matters

Plan limits are shared across Claude and Claude Code. A single resume of a large session could previously consume a meaningful part of a 5-hour window with no indication in advance. The warning turns that into an explicit choice, which is useful for anyone who keeps long-lived sessions open for days.