{"version":"2.1.246","anchor":"hook-and-command-paths-can-start-with-claude-plugin-root","canonical_anchor":"hook-and-command-paths-can-start-with-claude-plugin-root","heading":"Hook and command paths can start with $CLAUDE_PLUGIN_ROOT","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/hook-and-command-paths-can-start-with-claude-plugin-root","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Hook and command paths can start with $CLAUDE_PLUGIN_ROOT\n\nPlugin hooks and commands can point at files inside the plugin using $CLAUDE_PLUGIN_ROOT.\n\n**What**\n\nHooks and commands shipped by a plugin can now point at files inside the plugin itself, using `$CLAUDE_PLUGIN_ROOT` or `${CLAUDE_PLUGIN_ROOT}` at the start of the path.\n\n**Details**\n\n- The path validator accepts this prefix alongside the two it already allowed, `$HOME` and `$CLAUDE_PROJECT_DIR`.\n- Applies unconditionally, with no setting to turn it on.\n\n**Evidence**\n\n`$CLAUDE_PLUGIN_ROOT`\n\n- Area: Plugins\n- Names: `$CLAUDE_PLUGIN_ROOT`, `${CLAUDE_PLUGIN_ROOT}`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}