{"version":"2.1.311","anchor":"plugin-commands-skip-allowed-tools-naming-claude-project-dir","canonical_anchor":"plugin-commands-skip-allowed-tools-naming-claude-project-dir","heading":"Plugin allowed-tools naming CLAUDE_PROJECT_DIR are dropped when there is no folder","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/plugin-commands-skip-allowed-tools-naming-claude-project-dir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Plugin allowed-tools naming CLAUDE_PROJECT_DIR are dropped when there is no folder\n\nIn sessions with no project folder, plugin commands and skills lose any `allowed-tools` entry that names `CLAUDE_PROJECT_DIR`, and a warning is logged\n\n**Unclear.** Which kinds of session count as having no folder where tools run is not stated.\n\n**What**\n\nThis extends the same caution about plugin `allowed-tools` to another case. A plugin command's or skill's `allowed-tools` field lists tools it may use without asking you. Some sessions have no folder where tools run. In those sessions, Claude Code now drops any `allowed-tools` entry that names `CLAUDE_PROJECT_DIR`, the variable that stands for the project folder, and logs a warning. Before, every entry was kept.\n\n**Why**\n\nIf a plugin relies on a tool permission tied to the project folder, that permission will be missing in a session with no folder. The command will then ask before using that tool, or fail to use it.\n\n- Area: Plugins\n- Names: `allowed-tools`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}