{"version":"2.1.312","anchor":"windows-path-spelling-checks-added-to-config-dir-write-prote","canonical_anchor":"windows-path-spelling-checks-added-to-config-dir-write-prote","heading":"Windows paths are checked more carefully before writing to Claude Code's own folders","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/windows-path-spelling-checks-added-to-config-dir-write-prote","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Windows paths are checked more carefully before writing to Claude Code's own folders\n\nOn Windows, Claude Code now resolves alternate path spellings before writing to its protected folders, and may refuse a write it cannot trace\n\n**Unclear.** It is not clear which of the new checks depend on the server setting, or which run outside Windows.\n\n**What**\n\nClaude 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.\n\nOn 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.\n\n**Why**\n\nWindows users may see new write refusals with long explanations, including for paths that are actually harmless but cannot be traced.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}