{"version":"2.1.290","anchor":"plugin-package-install-pinned-to-the-plugin-folder-via-proc","canonical_anchor":"plugin-package-install-pinned-to-the-plugin-folder-via-proc","heading":"Plugin package installs on Linux and WSL stay locked to the plugin's folder","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/plugin-package-install-pinned-to-the-plugin-folder-via-proc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Plugin package installs on Linux and WSL stay locked to the plugin's folder\n\nOn Linux and WSL, plugin packages are installed through a held-open handle on the plugin folder, and the install stops if that folder is swapped\n\n**Unclear.** It is not clear which plugin install steps use this new method.\n\n**What**\n\nA plugin can need extra packages, which Claude Code installs into the plugin's folder. On Linux and WSL (Windows Subsystem for Linux), Claude Code now opens the plugin's folder first, refuses to follow a link while doing so, and installs the packages through that open folder rather than by its name.\n\nIf the folder was moved or replaced by a link during the install, the install stops with: the plugin's folder was moved or replaced by a link during the install, so the packages were not added. If Claude Code cannot confirm where the folder is, it reports that too. On other systems the install still uses the folder's plain path.\n\nBefore, Claude Code only checked after the install and showed the same message.\n\n**Why**\n\nThis closes a gap where something could swap the plugin's folder for a link to another location partway through an install, so packages could land somewhere unintended.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}