{"version":"2.1.292","anchor":"plugin-remove-explains-blocked-legacy-local-settings-file","canonical_anchor":"plugin-remove-explains-blocked-legacy-local-settings-file","heading":"Plugin removal says why a local settings file was not read","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/plugin-remove-explains-blocked-legacy-local-settings-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Plugin removal says why a local settings file was not read\n\nclaude plugin remove now explains why .claude\/settings.local.json was skipped: a link to another machine, an unreadable path, or a mid-read change\n\n**What**\n\n`.claude\/settings.local.json` is an older local settings file in the folder Claude Code was started in. When `claude plugin remove` cannot read it, the command now says which of these was the cause:\n\n- a link that leads to another machine\n\n- a path that could not be read\n\n- the file changed while it was being read\n\nBefore, it gave one general message to repair or delete the file.\n\n**Why**\n\nYou can see what to fix instead of deleting the file to be safe.\n\n- Area: Plugins\n- Names: `claude plugin remove`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}