{"version":"2.1.293","anchor":"remote-stream-reconnect-announces-returned-head-yields","canonical_anchor":"remote-stream-reconnect-announces-returned-head-yields","heading":"Remote sessions can now say \"returned\" after a long break","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/remote-stream-reconnect-announces-returned-head-yields","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Remote sessions can now say \"returned\" after a long break\n\nAfter a long gap or a forced redial, a remote session's connection can now announce \"returned\" instead of always \"reconnected\"\n\n**Unclear.** Whether a setting or server switch controls the new \"returned\" announcement is not known.\n\n**What**\n\nA remote session keeps a live connection to Claude Code. When that connection comes back, it used to always announce \"reconnected\". It can now announce \"returned\" instead, after a long gap or after Claude Code redials because the connection drifted.\n\nThe session loop also gains a new step.\n\n**Why**\n\nThis changes how remote sessions report their connection coming back.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}