{"version":"2.1.323","anchor":"out-of-bounds-file-permission-message-when-no-folders-are-al","canonical_anchor":"out-of-bounds-file-permission-message-when-no-folders-are-al","heading":"Clearer message when a session was started with no folders allowed","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/out-of-bounds-file-permission-message-when-no-folders-are-al","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Clearer message when a session was started with no folders allowed\n\nWhen a file is refused and no folders are allowed, the message now says the session was launched with none instead of showing an empty list\n\n**What**\n\nWhen Claude Code refuses to touch a file because it sits outside the folders it may use, the message lists those folders. If the session was started with no allowed folders at all, the message used to show an empty list. It now reads \"every folder that the file tools may use (this session was launched with none)\".\n\n**Why**\n\nThe old message left a blank where the folder list should be. The new one tells you directly that no folders were allowed for this session.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}