{"version":"2.1.299","anchor":"cold-resume-quota-prompt-uses-served-rate-limit-tier-and-cap","canonical_anchor":"cold-resume-quota-prompt-uses-served-rate-limit-tier-and-cap","heading":"Fewer false warnings about quota use when resuming an old session","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/cold-resume-quota-prompt-uses-served-rate-limit-tier-and-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Fewer false warnings about quota use when resuming an old session\n\nThe usage warning shown when resuming an old session now caps its estimate at the model's context size and can use your current rate-limit tier\n\n**What**\n\nWhen you resume an old session, Claude Code may warn you that picking it up again will use a lot of your usage quota, because the whole conversation has to be sent to the model again. The estimate behind that warning has changed in two ways:\n\n- The conversation size it counts is now capped at the most the model can hold at once, known as its context window.\n\n- It can use the rate-limit tier the server currently reports for your account, instead of the one Claude Code saved earlier. Your rate-limit tier sets how much you can use in a given period.\n\nThe second change is on unless a configuration value turns it off. When the current tier means no warning is needed but the saved tier would have shown one, the warning is not shown.\n\n**Why**\n\nYou should see the warning less often in cases where resuming would not actually use up your quota.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}