{"version":"2.1.275","anchor":"working-directory-anchors-now-support-multiple-session-worki","canonical_anchor":"working-directory-anchors-now-support-multiple-session-worki","heading":"Working-directory anchors now support multiple session working directories, not just one","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/working-directory-anchors-now-support-multiple-session-worki","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Working-directory anchors now support multiple session working directories, not just one\n\nPath validation for publishing and reading artifacts now accounts for multiple session working directories, not just one\n\n**What**\n\nClaude Code validates file paths against a set of allowed \"anchor\" locations, such as the current working directory, when checking where artifacts can be published or read from. Previously this logic assumed a single working directory plus a scratchpad. It now works from a general list that also includes any additional configured working directories, each labeled by kind (`cwd`, `dir`, or `scratchpad`). Error messages about disallowed paths now list all of the session's working directories instead of just one.\n\n**Why**\n\nSessions that work across more than one directory get accurate validation and clearer error messages instead of being checked against only a single assumed location.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}