All AI updates

Claude Code warns Pro and Max users when resuming would use a noticeable share of the 5-hour limit

Claude Code v2.1.304, released October 19, 2026, warns Pro and Max users when resuming an inactive conversation would use a noticeable share of the 5-hour usage limit. You can resume anyway or start a new conversation. /usage now says when a rate limit on usage data ends.

SessionWatcher editorial · Published · Updated · Source announcement: 2026-10-19

Related guide: How to check your Claude Code usage

Resume warning on Pro and Max plans

Claude Code v2.1.304 was released on GitHub on October 19, 2026. It adds a warning on Pro and Max plans that appears when resuming an inactive conversation would use a noticeable share of your 5-hour usage limit.

The warning gives two choices. You can resume anyway, or you can start a new conversation. If you start a new one, Claude can look up the previous conversation when you refer to it.

The release notes do not say what counts as a noticeable share. They also do not describe any change to the size of the 5-hour limit, the weekly limit or reset times, and they mention the warning only for Pro and Max plans.

Sources: v2.1.304

/usage now says when its usage-data rate limit ends

When usage data is rate limited, /usage now says when that rate limit ends. Before, it showed the message "try again in a moment".

Sources: v2.1.304

Other changes tied to cache and token use

The release fixes a timing problem with self-paced /loop wakeups scheduled at the 1-hour maximum. They used to fire just after the 1-hour prompt cache expired. Now they no longer re-read the conversation uncached.

Another fix covers resumed and cloud sessions, which sent Claude the whole skill list again each time plugins reloaded at startup. The release also removes the "(research preview)" label from the /fast dialog title on Opus 5.5.

Sources: v2.1.304

AI assisted reporting, checked against the linked official sources. Source pages checked 2026-10-19. Editorial process and corrections.