{"version":"2.1.312","anchor":"new-idle-released-exit-reason-and-ccr-file-copy-notes","canonical_anchor":"new-idle-released-exit-reason-and-ccr-file-copy-notes","heading":"Remote sessions add a clean idle exit and a note about files still copying","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/new-idle-released-exit-reason-and-ccr-file-copy-notes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote sessions add a clean idle exit and a note about files still copying\n\nA remote session released for being idle now exits cleanly, and you are told when files are still being copied\n\n**What**\n\nIn remote sessions:\n\n- A session released for being idle (`idle_released`) is now treated as a normal finish and exits with code 0, meaning success.\n\n- While a tool call is waiting, Claude Code can now tell you that some files are still being copied into place.\n\n**Why**\n\nAn idle remote session ending no longer counts as a failure, and a wait caused by copying files is explained instead of looking stuck.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}