Claude Code Cold Resume Uses 5–7% of Usage Limit
Summary
Pixel shares measured results on how resuming idle Claude Code sessions affects usage limits. Two Opus 5.5 sessions with 170–210k tokens of context each used 5–7% of the 5-hour limit and 1% of the weekly limit; the first two requests rewrote conversation context to cache.
DEV Community
claude --resume Used 7% of My 5-Hour Limit (Measured)
Claude Code subscriptions have two limits: a 5-hour window and a weekly limit, both shown as a percentage used. Everyone says resuming a cold session is expensive. I wanted to know how expensive in the units that actually lock you out, so I resumed two idle sessions one at a time and logged both meters and the token counts of every request. Result: each cold resume took 5–7% of my 5-hour limit and 1% of my weekly limit. Both sessions were Opus 5.5 with 170–210k tokens of context. In both, the first two requests after the resume each wrote the whole conversation to the cache, so the second write was about half of the cost. Setup Plan and model: the $30-a-month Claude plan, Claude Code 2.1.285, Opus 5.5, 1-hour prompt cache. Meters: Claude Code passes rate_limits.five_hour.used_percentage and rate_limits.seven_day.used_percentage to the statusline on every refresh. A statusline script appended each change to a log with a timestamp. Tokens: every assistant reply in the session's JSONL transcript has a usage record: tokens written to cache (cache_creation_input_tokens), read from cache (cache_read_input_tokens), new input and output. Baseline: 5-hour 12%, weekly 42% at 15:27 (local time). No other sessions or subagents were running. One source of noise: the session I measured from was also open. Its own requests are in the meter readings: about 15% of all usage during the run, roughly 2.5 points of the 5-hour meter. I separate it out below. Session A: 210k tokens, idle 2.5 days Last request on November 13. I resumed it at 15:32 and sent one message. When it started a tool call I pressed Esc, and it replied once more. Request Time Written to cache Read from cache Output 5-hour Weekly 1. Reply to my message 15:32:26 209,269 0 508 12% → 16% 42% → 43% 2. Reply after Esc 15:35:02 190,989 24,880 70 17% → 21% 43% The meter moved 12% → 21%. Leaving out the measuring session, Session A's own requests account for about 7 points of the 5-hour limit, and the weekly limit moved 1 point. Session B: 183k tokens, idle 12 days Last request on November 4. My first message was stopped by L2Cache's cold-resume guard ("stopped this message so it doesn't reload 183k tokens"). No request was sent, so that cost nothing. I sent it again at 15:38:12. The model replied and kept working, so requests 2 and 3 came 10 and 16 seconds after the first. Request Time Written to cache Read from cache Output 5-hour Weekly 1 15:38:41 143,581 25,103 289 21% → 24% 43% → 44% 2 15:38:51 146,688 24,880 161 24% → 27% 44% 3 15:38:57 1,283 171,568 284 27% → 28% 44% Next 8 requests to 15:40:59 13,187 total 1,777,660 total 3,564 28% → 29% 44% The two cache writes took the 5-hour meter from 21% to 27%: about 5 points once the measuring session is left out. The weekly limit moved 1 point. The next eight requests, all reading the warm cache, cost about 2 points together. The second write In both sessions the second request read only about 25k tokens from cache, which is the system prompt and tool definitions, and wrote the conversation again. In Session B that happened 10 seconds after the first write, with no Esc involved. The transcript doesn't record why. From the third request on, reads covered the full context as normal. What one point is worth Anthropic doesn't publish how the plan meters weight tokens. If I weight them by Opus API price ratios (input 1×, 1-hour cache write 2×, cache read 0.1×, output 5×), every request in the run comes to about 1.92 million input-token equivalents, and the 5-hour meter moved 17 points: Source Input-token equivalents Share of 5-hour points Session A (2 requests) 805,898 ~7 Session B (11 requests) 830,917 ~7 (5 from the two writes) Measuring session 281,974 ~2.5 Total 1,918,789 17 5-hour limit: about 110k Opus input-token equivalents per point on the $30 plan. A 200k-token Opus session written to cache once is roughly 4 points; written twice, as here, roughly 7. Weekly limit: it ticked over twice in the run, at 5-hour readings of 16% and 2...

Powered by Readybot.io