You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.296,
ImprovementsSection of the release
What
This 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.
A remote kill switch, a server-side setting that can turn the behaviour off, can stop this exit from happening.
Why
Without 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.
