{"version":"2.1.311","anchor":"skills-allowed-tools-claude-project-dir-fallback-message-an","canonical_anchor":"skills-allowed-tools-claude-project-dir-fallback-message-an","heading":"Skill allowed-tools warning reworded and folder lookup prefers the session's folder","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/skills-allowed-tools-claude-project-dir-fallback-message-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Skill allowed-tools warning reworded and folder lookup prefers the session's folder\n\nThe `CLAUDE_PROJECT_DIR` fallback warning now says the process has no folder where tools run, and the lookup prefers a session's folder\n\n**What**\n\nWhen a skill's `allowed-tools` (the tools it may use without asking you) depend on `CLAUDE_PROJECT_DIR` and no folder can be found, Claude Code shows a warning. Its wording changed from \"because this session has no working directory\" to \"because this process has no folder where the tools run\".\n\nWhen working out that folder, Claude Code now prefers a folder tied to the session, if there is one.\n\n**Why**\n\nThe way the project folder is found changed for processes running without a screen or remotely, and the warning now describes that case more accurately.\n\n- Area: Skills\n- Names: `allowed-tools`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}