{"version":"2.1.311","anchor":"plugin-claude-project-dir-substitution-is-now-conditional-an","canonical_anchor":"plugin-claude-project-dir-substitution-is-now-conditional-an","heading":"Plugins using ${CLAUDE_PROJECT_DIR} can now fail instead of using a fallback folder","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/plugin-claude-project-dir-substitution-is-now-conditional-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Plugins using `${CLAUDE_PROJECT_DIR}` can now fail instead of using a fallback folder\n\nWhen the project folder can't be found, ${CLAUDE_PROJECT_DIR} in a plugin is no longer replaced with another folder and an error is raised instead\n\n**What**\n\nPlugins are add-ons for Claude Code. A plugin can write `${CLAUDE_PROJECT_DIR}`, and Claude Code replaces it with the path of your project folder. That replacement now happens only when the project folder is known. If looking up the project folder comes back empty, Claude Code now raises an error, where it used to fill in another folder instead.\n\n**Why**\n\nPlugin hooks (commands a plugin runs automatically) that rely on `${CLAUDE_PROJECT_DIR}` may now stop with an error in situations where they previously ran with a substitute folder.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}