{"version":"2.1.302","anchor":"plugin-bin-path-entries-containing-the-path-delimiter-are-dr","canonical_anchor":"plugin-bin-path-entries-containing-the-path-delimiter-are-dr","heading":"Plugin folders with a path separator in their name no longer break PATH","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/plugin-bin-path-entries-containing-the-path-delimiter-are-dr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Plugin folders with a path separator in their name no longer break PATH\n\nClaude Code now skips plugin program folders whose path contains the PATH separator character, and skips folders already on PATH\n\n**What**\n\nPATH is the list of folders your computer searches for programs to run. Plugins can bring their own programs, and Claude Code adds each plugin's program folder to PATH. Entries in PATH are separated by a special character (a colon on macOS and Linux, a semicolon on Windows).\n\nWhen adding plugin folders, Claude Code now:\n\n- skips any folder whose path itself contains that separator character, and logs \"Dropping plugin bin path that holds the PATH delimiter:\"\n\n- skips any folder that is already on PATH\n\nIn PowerShell, Claude Code now clears its stored list of plugin folders before reading the shell's settings again, so the list is rebuilt fresh.\n\n**Why**\n\nA folder name containing the separator would be read as two separate entries and could mess up the whole PATH. Skipping it keeps your other programs findable.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}