{"version":"2.1.314","anchor":"ccr-v2-resume-now-fails-closed-when-history-cant-be-loaded","canonical_anchor":"ccr-v2-resume-now-fails-closed-when-history-cant-be-loaded","heading":"Resumed remote sessions can refuse to start when their history fails to load","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/ccr-v2-resume-now-fails-closed-when-history-cant-be-loaded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Resumed remote sessions can refuse to start when their history fails to load\n\nA resumed remote session can refuse to start if its saved conversation cannot be read or restored, instead of continuing empty\n\n**Unclear.** Whether the refusal is switched on for a given account is decided on Anthropic's servers and has not been read.\n\n**What**\n\nWhen you resume a remote session, Claude Code loads its earlier conversation. A remote session is one that runs on a remote machine instead of your own. That loading step now reports why it ended: history found, no history, nothing to read it with, the read failed, or restoring it failed.\n\nIf the history could not be read or restored, Claude Code can now refuse to start and show: \"the session's conversation history could not be read from CCR; not starting without it\". This refusal is controlled by a switch set on Anthropic's servers. Without it, Claude Code only records the problem and goes on. A read failure for the first worker on a session never blocks it.\n\n**Why**\n\nBefore, a remote session could resume with an empty conversation and give no sign that anything was lost. With the refusal in place, you are told instead of quietly losing context.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}