You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.312,
ImprovementsSection of the release
Unclear It is not clear which of the new checks depend on the server setting, or which run outside Windows.
What
Claude Code blocks its file tools from writing into some of its own folders and files: the jobs, daemon, shell-snapshots and session-env folders, and daemon.json. That guard now understands Windows path spellings. It follows aliases and links, such as Windows short names like ADOPT~1.JSO, up to a fixed number of lookups.
On Windows it can now refuse a write when it cannot work out where a path leads. New refusal messages explain why, including ones that begin "Refusing to write". Part of these checks depends on a setting Claude Code reads from its server.
Why
Windows users may see new write refusals with long explanations, including for paths that are actually harmless but cannot be traced.
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 doubtIt is not clear which of the new checks depend on the server setting, or which run outside Windows.
