{"version":"2.1.282","anchor":"cold-resume-quota-warning-dialog-built-but-inert-under-the-c","canonical_anchor":"new-cold-resume-quota-warning-when-resuming-a-long-idle-con","heading":"New warning before resuming a long, idle conversation that would use much of the 5-hour limit","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/cold-resume-quota-warning-dialog-built-but-inert-under-the-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### New warning before resuming a long, idle conversation that would use much of the 5-hour limit\n\nResuming a large, long-idle conversation can show how much of your 5-hour usage limit it will use, offering a fresh conversation instead\n\n**Unclear.** One further condition that can skip the dialog was not worked out.\n\n**What**\n\nWhen you resume a conversation that has been inactive for a while and is large, Claude Code can now show a dialog before continuing. It reads \"This conversation has been inactive for\" a duration \"and is\" a number of \"tokens long.\", then \"Resuming it will use about\" a percentage \"of your 5-hour usage limit.\", or \"all\" when the estimate is 100% or more.\n\n- The choices are \"Resume\" and \"Start a new conversation\". The dialog can also be dismissed. Starting a new conversation runs `\/clear`.\n\n- The estimate uses the conversation's context tokens, the model and your rate-limit tier, with per-tier `fiveHourCredits` and per-model `creditsPerMillionTokens` tables from the remote config `tengu_amber_tally`. Both tables need an entry for your tier and model.\n\n- The built-in default of `tengu_amber_tally` is empty and does not pass validation, so the dialog cannot appear until the tables are supplied remotely. Nothing has been read about this config yet.\n\n- It does not appear when the estimate is below `minPercent` (which falls back to 5), when the `resumeReturnDismissed` setting is set, or when the model is unchanged and the prompt cache still looks warm. There is one more failure check the members did not resolve.\n\n- It runs after the existing stale-resume dialog that offers `\/compact`, only when that dialog does not apply or returns \"skipped_no_summary\". That earlier step is now asynchronous.\n\n**Why**\n\nResuming a large conversation after a long break sends its whole context again, which can take a large share of a subscriber's 5-hour usage limit without warning. This gives a chance to start fresh instead.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}