{"version":"2.1.321","anchor":"remote-session-worker-disconnect-only-ends-the-start-for-c","canonical_anchor":"remote-session-worker-disconnect-only-ends-the-start-for-c","heading":"Remote sessions handle a disconnected worker differently","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-session-worker-disconnect-only-ends-the-start-for-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote sessions handle a disconnected worker differently\n\nA disconnected remote worker now ends a startup only when a new worker was being created\n\n**What**\n\nIn a remote session, Claude Code runs on a separate machine, called a worker. When a worker reports that it has disconnected, Claude Code now ends the startup in progress only if it was creating a new worker. Before, it ended the startup whenever a worker had been seen on that connection.\n\nMessages confirming delivery can now say a message was processed but not run.\n\n**Why**\n\nThis changes how Claude Code handles workers restarting during a remote 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"}