{"version":"2.1.317","anchor":"new-permissionsworkingdirectoriesasgiven-setting-for-host-p","canonical_anchor":"new-permissionsworkingdirectoriesasgiven-setting-for-host-p","heading":"New permissions.workingDirectoriesAsGiven setting for programs that launch Claude Code","tier":"use","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/new-permissionsworkingdirectoriesasgiven-setting-for-host-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### New `permissions.workingDirectoriesAsGiven` setting for programs that launch Claude Code\n\nA host program can now pass working directories spelled exactly as given, via --settings, without Claude Code following links\n\n**What**\n\nA new setting, `permissions.workingDirectoriesAsGiven`, lists working directories spelled exactly as they were passed in, without following links to other locations. A working directory is a folder Claude Code is allowed to work in.\n\nThe setting is only read from:\n\n- The `--settings` flag\n\n- Settings sent by the program that launched Claude Code\n\nIt is ignored in user, project, local and managed settings files. It does not add any working directory and does not allow anything on its own.\n\n**Why**\n\nThis is meant for editors, IDEs and other programs that launch Claude Code through the SDK. It helps most on Windows, where mapped network drives and paths that ignore upper and lower case can make the same folder appear under different spellings.\n\n- Area: Permissions\n- Names: `permissions.workingDirectoriesAsGiven`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}