{"version":"2.1.314","anchor":"auto-resume-rearm-cap-now-counts-continuations-since-the-las","canonical_anchor":"auto-resume-rearm-cap-now-counts-continuations-since-the-las","heading":"Automatic resume after usage limits is now capped per human prompt","tier":"notice","area":"Usage & Limits","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/auto-resume-rearm-cap-now-counts-continuations-since-the-las","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Automatic resume after usage limits is now capped per human prompt\n\nAuto-resume after a usage limit now stops after a set number of automatic continuations since your last prompt, instead of counting consecutive re-arms\n\n**What**\n\nClaude Code can automatically resume work after a usage quota resets. Each automatic continuation now increases a counter, `continuationsSinceHumanPrompt`, that tracks how many times work continued on its own since you last typed a prompt.\n\n- The quota auto-resume check now compares `continuationsSinceHumanPrompt` with its cap. Before, it compared `consecutiveRearms`, the number of back-to-back re-arms.\n\n- The check that sets up the next automatic continuation now stops once the counter reaches the cap and records the reason as `continuation_cap`. Before, there was no such cap at this step.\n\n- The handling when the cap is reached moved into a shared helper, replacing the earlier inline code.\n\n**Why**\n\nThis changes when automatic resumption stops: the limit now applies to all automatic follow-ups between your own prompts, so a session cannot keep continuing indefinitely without you.\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}