{"version":"2.1.284","anchor":"settings-file-watcher-skips-directories-that-lead-onto-netwo","canonical_anchor":"settings-file-watcher-skips-directories-that-lead-onto-netwo","heading":"Settings folders that lead to network drives are no longer watched for changes","tier":"notice","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/settings-file-watcher-skips-directories-that-lead-onto-netwo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Settings folders that lead to network drives are no longer watched for changes\n\nClaude Code stops watching a settings folder for edits if the folder, or a link inside it, leads onto a network path\n\n**What**\n\nWhile it runs, Claude Code watches the folders holding your settings files so it can pick up edits without a restart. Before it starts watching a folder, it now checks that neither the folder nor any symlink inside it leads onto a network path. A symlink is a file that points to another location.\n\nIf the check fails, or cannot be completed, that folder is not watched for the rest of the session, and Claude Code writes a line to its debug log saying so. Before, every settings folder was watched.\n\n**Why**\n\nThis keeps Claude Code from reaching into network mounts, such as the macOS `\/Network` or `\/.vol` paths, just because a settings symlink points there. The catch is that edits to settings in such a folder are not picked up until you restart the session.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}