{"version":"2.1.302","anchor":"win32-and-macos-directory-anchored-filesystem-backends-added","canonical_anchor":"win32-and-macos-directory-anchored-filesystem-backends-added","heading":"Groundwork for safer file operations on Windows and macOS","tier":"internal","area":"File System","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/win32-and-macos-directory-anchored-filesystem-backends-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Groundwork for safer file operations on Windows and macOS\n\nNew code for safer file operations on Windows and macOS is added, but nothing in Claude Code uses it yet\n\n**What**\n\nClaude Code adds new code for Windows and macOS that opens, renames, links and deletes files relative to a folder it already holds open. It accepts only plain file names, so names like `.`, `..`, or names containing a path separator or `:` are refused.\n\nOn macOS this needs a feature the runtime (the program that runs Claude Code) may not have. Without it, the macOS version does not start and logs a warning. Nothing in Claude Code is shown to use this code yet.\n\n**Why**\n\nThis is groundwork for file operations that are harder for another program to interfere with mid-operation. Nothing changes for you yet.\n\n- Area: File System\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}