{"version":"2.1.304","anchor":"exit-in-a-remoteattached-session-path","canonical_anchor":"exit-in-a-remoteattached-session-path","heading":"Quitting now takes a separate path in attached sessions","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/exit-in-a-remoteattached-session-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Quitting now takes a separate path in attached sessions\n\nWhen you exit while attached to another session, Claude Code now handles the exit separately\n\n**Unclear.** What the separate exit path does differently for an attached session is not clear.\n\n**What**\n\nWhen you exit or quit, Claude Code now first checks whether you are attached to a session. Attached means connected to a session running somewhere else. If you are, the exit is handled by a separate path. Other exits work as before.\n\n**Why**\n\nExiting behaves differently when you are attached to a session.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}