{"version":"2.1.290","anchor":"settings-file-symlinks-tracked-for-write-permission-prompts","canonical_anchor":"settings-file-symlinks-tracked-for-write-permission-prompts","heading":"Writes that reach a settings file through a link now always ask first","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/settings-file-symlinks-tracked-for-write-permission-prompts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Writes that reach a settings file through a link now always ask first\n\nA file write that leads to a Claude Code settings file through a symbolic link now triggers a permission prompt and cannot be auto-approved\n\n**What**\n\nA symbolic link (symlink) is a file that points to another file. Claude Code already asked before writing directly to one of its own settings files. It now also tracks links that lead to those files. If Claude tries to write to a path that ends up at a settings file through a link, you get a permission prompt saying the Claude Code settings file leads there through a link.\n\nAutomatic approval can no longer approve these writes. File paths shown in permission messages are also now formatted more consistently.\n\n**Why**\n\nBefore, a write through a link could get past the check that protects settings files. This closes that gap, so changes to your settings always go past you.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}