{"version":"2.1.295","anchor":"reconnect-no-longer-drops-permission-prompt-gated-redelivere","canonical_anchor":"reconnect-no-longer-drops-permission-prompt-gated-redelivere","heading":"Reconnecting keeps messages that were waiting on a permission prompt","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/reconnect-no-longer-drops-permission-prompt-gated-redelivere","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Reconnecting keeps messages that were waiting on a permission prompt\n\nMessages sent again after a reconnect are no longer dropped when they were waiting behind a permission prompt, and Stop also cancels waiting messages\n\n**What**\n\nWhen a remote or headless session reconnects, messages may be sent to it a second time, and Claude Code removes the duplicates. That handling now covers more cases:\n\n- Messages that were summarised away\n\n- Messages waiting behind a permission prompt (a question asking whether Claude may take an action)\n\n- Messages put back on the input to run again\n\nA Stop that arrives before a permission answer is now tracked, and the Stop is kept for that answer. An interrupt also cancels messages that are waiting to run.\n\n**Why**\n\nResuming and interrupting remote and headless sessions (those run with no interactive screen) should be more reliable.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}