You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.314,
ImprovementsSection of the release
Unclear Whether the refusal is switched on for a given account is decided on Anthropic's servers and has not been read.
What
When 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.
If 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.
Why
Before, 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether the refusal is switched on for a given account is decided on Anthropic's servers and has not been read.
