{"version":"2.1.321","anchor":"remote-worker-stopwork-becomes-abortable-declined-sessions","canonical_anchor":"remote-worker-stopwork-becomes-abortable-declined-sessions","heading":"Declined remote sessions are now marked \"Couldn't start\" and archived","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-worker-stopwork-becomes-abortable-declined-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Declined remote sessions are now marked \"Couldn't start\" and archived\n\nWhen a remote session is declined, Claude Code now stops its work, marks it refused with the title \"Couldn't start\" and archives it\n\n**What**\n\nWhen a remote session is declined, Claude Code now stops its work and marks the session refused, with the title \"Couldn't start\". It then archives the session, moving it out of the active list. Retries of stopping that work can now also be cancelled partway through, which they could not be before.\n\n**Why**\n\nDeclined remote sessions are cleaned up instead of being left behind.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}