{"version":"2.1.302","anchor":"powershell-plugin-bin-paths-added-to-spawn-environment","canonical_anchor":"powershell-plugin-bin-paths-added-to-spawn-environment","heading":"PowerShell commands now get plugin program folders passed to them","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/powershell-plugin-bin-paths-added-to-spawn-environment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### PowerShell commands now get plugin program folders passed to them\n\nWhen Claude Code runs a PowerShell command, it now passes along the folders where installed plugins keep their programs\n\n**Unclear.** It is not confirmed that plugin programs become runnable by name in PowerShell, for example by being added to the search path.\n\n**What**\n\nPlugins are add-ons that extend Claude Code, and some ship their own programs. When Claude Code starts a PowerShell command, it now works out the folders holding those plugin programs and passes them to the command's environment, the set of settings a program starts with.\n\n**Why**\n\nThis affects whether programs that come with plugins can be run from the PowerShell tool.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}