{"version":"2.1.287","anchor":"add-dir-rejection-message-now-refers-to-the-sessions-workin","canonical_anchor":"add-dir-rejection-message-now-refers-to-the-sessions-workin","heading":"The --add-dir rejection message now names the session's working directory","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/add-dir-rejection-message-now-refers-to-the-sessions-workin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### The `--add-dir` rejection message now names the session's working directory\n\nA directory outside the allowed area is now rejected with wording about the session's working directory instead of \"cwd\"\n\n**Unclear.** It is not clear whether the rewritten check now accepts or rejects any paths differently.\n\n**What**\n\n`--add-dir` lets Claude read and edit files in extra folders. When a directory is rejected because it is outside the allowed area, the message now says it is not a subdirectory of the session's working directory or of a launch-time `--add-dir` root. Before, it said \"cwd\".\n\nThe check behind it was also rewritten. It now compares against the session's own working directory and uses a shared comparison step.\n\n**Why**\n\nIf you hit this error, the message says plainly which folder it compared against.\n\n- Area: Permissions\n- Names: `--add-dir`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}