{"version":"2.1.323","anchor":"folder-block-denial-may-name-an-add-folder-hint-behind-tengu","canonical_anchor":"folder-block-denial-may-name-an-add-folder-hint-behind-tengu","heading":"Folder-blocked messages may explain how to add the folder","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/folder-block-denial-may-name-an-add-folder-hint-behind-tengu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Folder-blocked messages may explain how to add the folder\n\nWhen a folder is blocked, the main session's denial message can now tell you how to add that folder, behind a setting that is off by default\n\n**What**\n\nSometimes Claude Code refuses to work with a file because it is in a folder Claude Code has not been given access to. When that happens in your main conversation, the refusal can now include a note telling you how to add that folder. It does not happen inside a subagent, which is a helper Claude Code starts to handle part of a task on its own.\n\nThe new wording sits behind a remotely controlled switch. The code treats that switch as off when no server setting arrives.\n\n**Why**\n\nRight now a blocked folder can leave you unsure how to fix it. The new wording points you to the next step.\n\n- Flag `tengu_amber_doorbell`: Not enough to say (read for one account on one subscription tier against v2.1.323; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}