{"version":"2.1.318","anchor":"remote-session-send-path-no-longer-wedges-after-a-failed-or","canonical_anchor":"remote-session-send-path-no-longer-wedges-after-a-failed-or","heading":"A failed message send in a remote session no longer leaves it stuck sending","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/remote-session-send-path-no-longer-wedges-after-a-failed-or","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### A failed message send in a remote session no longer leaves it stuck sending\n\nWhen a message fails to send in a remote session, Claude Code now resets its sending state and its response timer\n\n**What**\n\nA remote session is a Claude Code session that runs on another machine and that you connect to. When sending a message to it fails, Claude Code now clears the state that marks a message as being sent, and resets the timer that waits for a reply. Before, a failure did not clear the sending state.\n\n**Why**\n\nA failed send should no longer leave the session looking as if it is still sending, for example with a spinner or a queue that never clears.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}