{"version":"2.1.292","anchor":"pluginskill-off-settings-check-reads-legacy-and-added-dir-s","canonical_anchor":"pluginskill-off-settings-check-reads-legacy-and-added-dir-s","heading":"Plugin-off check reads some settings files more carefully","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/pluginskill-off-settings-check-reads-legacy-and-added-dir-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Plugin-off check reads some settings files more carefully\n\nWhen working out why plugins are still on, Claude Code now reads the legacy local settings file and added-directory settings through a guarded reader\n\n**What**\n\nClaude Code has a check that works out why plugins have not been turned off. That check now reads two kinds of settings file through a guarded reader, one that can refuse a file instead of opening it directly:\n\n- the legacy local settings file\n\n- the settings files of added directories, which are extra folders you have given Claude Code access to\n\nIf the reader refuses a file, Claude Code logs that it counted the file as present anyway. It also notes whether an added directory's settings file is behind a link, meaning a symbolic link that points somewhere else.\n\n**Why**\n\nThis makes these settings reads safer when a file is a link to another place or sits on a network drive.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}