{"version":"2.1.307","anchor":"remote-task-stop-and-sse-reconnect-tweaks","canonical_anchor":"remote-task-stop-and-sse-reconnect-tweaks","heading":"Remote sessions record all task stops and can reconnect faster","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/remote-task-stop-and-sse-reconnect-tweaks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Remote sessions record all task stops and can reconnect faster\n\nRemote task stops are now recorded whoever made them, the remote client calls itself \"client\", and some live connections retry without waiting\n\n**What**\n\nWhen a running task is stopped in a remote session, Claude Code now records the stop whatever caused it. Before, it recorded it only when a person stopped it. The remote client also now identifies itself as \"client\" instead of \"user\".\n\nRemote sessions get updates over a live connection that the server keeps open and pushes messages through. When that connection drops, Claude Code waits a little longer after each failed attempt before trying again. Depending on the kind of connection, it can now reset that waiting time and reconnect straight away.\n\n**Why**\n\nThese are small changes to how remote sessions behave. A stop made by a connected app is no longer missed.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}