{"version":"2.1.312","anchor":"remote-session-end-session-can-carry-leftfor-released-and","canonical_anchor":"remote-session-end-session-can-carry-leftfor-released-and","heading":"Remote sessions can end as \"released\" and describe a copy of the folder","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/remote-session-end-session-can-carry-leftfor-released-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote sessions can end as \"released\" and describe a copy of the folder\n\nRemote sessions can now end with the reason \"released\", and can carry details of a separate copy of the working folder\n\n**What**\n\nA remote session is one where Claude Code is controlled from another device. Two things change:\n\n- When such a session ends for one particular reason, it is now marked as having left because it was \"released\".\n\n- A session can now carry optional details of a separate copy of its folder: the platform, the folder path and the home folder path.\n\n**Why**\n\nRemote sessions can now say more about how they ended and about any separate copy of the folder they are working on.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}