{"version":"2.1.305","anchor":"resume-treats-a-trailing-local-bash-command-or-local-command","canonical_anchor":"resume-treats-a-trailing-local-bash-command-or-local-command","heading":"Resuming a session that ended on your own shell command no longer looks interrupted","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/resume-treats-a-trailing-local-bash-command-or-local-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Resuming a session that ended on your own shell command no longer looks interrupted\n\nResuming a session whose last entry is a shell command you ran yourself, or its output, is now handled as that case rather than an interrupted prompt\n\n**What**\n\nWhen you resume a session, Claude Code looks at how the conversation ended to decide whether Claude was cut off mid-reply. It now checks whether the last entry is a local command, meaning a shell command you ran yourself (for example with `!`) or that command's output.\n\n- In most of those cases the session is now treated as ending on your local command, not as an interrupted turn.\n\n- In the remaining case it still reports an interrupted turn, but records that the turn ended on a shell command.\n\nBefore, these sessions were treated like any other prompt that was cut off.\n\n**Why**\n\nIf your last action before leaving was running a shell command yourself, resuming should no longer treat that as Claude being interrupted and pick the turn back up.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}