{"version":"2.1.296","anchor":"remote-worker-refuses-to-start-a-turn-when-stored-session-st","canonical_anchor":"remote-worker-refuses-to-start-a-turn-when-stored-session-st","heading":"Resumed remote sessions stop instead of running without their saved state","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/remote-worker-refuses-to-start-a-turn-when-stored-session-st","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Resumed remote sessions stop instead of running without their saved state\n\nWhen a resumed remote session cannot read its saved state, Claude Code now exits with an error instead of starting a turn with nothing\n\n**What**\n\nThis applies when Claude Code resumes a remote session, for example in `--print` mode, where it runs a single request without the interactive screen, or when another program drives it through the Agent SDK. Claude Code loads the session's stored state, which includes its history. If that state cannot be read, the worker (the process doing the work) now waits and then exits with an error. The error says it could not read the session's stored state and will not start a turn without it, and carries the code `worker_state_unread`.\n\nA remote kill switch, a server-side setting that can turn the behaviour off, can stop this exit from happening.\n\n**Why**\n\nWithout this check, a remote session could carry on as if it had an empty history, with no sign that anything was lost. Stopping with a clear error makes the problem visible.\n\n- Area: Sessions\n- Names: `--print`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}