{"version":"2.1.301","anchor":"systeminit-now-reports-original-cwd-and-additional-director","canonical_anchor":"systeminit-now-reports-original-cwd-and-additional-director","heading":"SDK start-up message now lists the session's permission folder and added folders","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/systeminit-now-reports-original-cwd-and-additional-director","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### SDK start-up message now lists the session's permission folder and added folders\n\nThe message an SDK session sends at start-up can now include the folder permission checks start from and any added working folders\n\n**What**\n\nWhen a session run through the Agent SDK starts, Claude Code sends a start-up message describing it. This message can now include two optional fields, marked as internal:\n\n- `original_cwd`: the folder that file permission checks start from\n\n- `additional_directories`: folders added to the session with `--add-dir`, through settings and in similar ways\n\nBoth fields are left out on redacted connections and for organizations covered by HIPAA, the US health-privacy rules. Folders added only by settings that come with the repository are not listed. The saved session state now holds these two values too, when they are set.\n\n**Why**\n\nPrograms that host Claude Code can learn from the start-up message which folder permissions are based on and which extra folders are open.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}