{"version":"2.1.290","anchor":"interrupted-prompt-resume-and-control-request-truncation-log","canonical_anchor":"interrupted-prompt-resume-and-control-request-truncation-log","heading":"Changes to resuming an interrupted prompt","tier":"notice","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/interrupted-prompt-resume-and-control-request-truncation-log","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Changes to resuming an interrupted prompt\n\nThe rules for when an interrupted prompt can be resumed, and for cutting a conversation at a pending request, have changed\n\n**Unclear.** What difference users will see when resuming is not known.\n\n**What**\n\nClaude Code now uses different rules to decide when a prompt that was interrupted can be resumed. When it cuts a conversation short at a request still waiting for an answer, it now records what kind of request it was and which tool it was for, and applies that cut only in narrower conditions than before.\n\n**Why**\n\nThis likely affects whether resuming a session, and replying after resuming, works correctly.\n\n- Area: Resume\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}