{"version":"2.1.323","anchor":"remote-attach-can-resume-only-after-restart-and-abort-on-inp","canonical_anchor":"remote-attach-can-resume-only-after-restart-and-abort-on-inp","heading":"Attaching to a cloud session can resume after a restart and stops cleanly","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-attach-can-resume-only-after-restart-and-abort-on-inp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Attaching to a cloud session can resume after a restart and stops cleanly\n\nAttaching to a cloud session can now just resume the link after a restart, and the attach stops when the session's input closes\n\n**What**\n\nThe request that attaches Claude Code to a cloud session, `attachServeRequest`, now accepts `resumeOnly`. With it, the link is resumed after a restart instead of being set up from scratch.\n\nOther changes to attaching:\n\n- An attach in progress is now cancelled when the session ends or its input closes.\n\n- Claude Code records whether the session runs on a Claude Code server.\n\n- Certain errors, such as the session history not being readable, are now reported as a refusal.\n\n**Why**\n\nRemote sessions served this way should recover better after a restart and stop cleanly instead of hanging.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}