{"version":"2.1.281","anchor":"set-cwd-sdk-control-request-documents-that-sessionstart-hook","canonical_anchor":"set-cwd-sdk-control-request-documents-that-sessionstart-hook","heading":"set_cwd SDK control request documents that SessionStart hooks never re-run","tier":"internal","area":"SDK","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/set-cwd-sdk-control-request-documents-that-sessionstart-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### set_cwd SDK control request documents that SessionStart hooks never re-run\n\nThe set_cwd control request is now documented as never re-running SessionStart hooks\n\n**What**\n\nPrograms that embed Claude Code can send a `set_cwd` request to change the folder it works in. The internal description of that request now states that it never re-runs `SessionStart` hooks, which are commands set to run when a session begins or resumes. Hosts that do not yet know which folder to use should start with `--await-claim` and then send `claim_session`.\n\n**Why**\n\nAnyone building on Claude Code learns that changing the folder later will not trigger their start-up hooks, and which route to use so the hooks run in the right folder.\n\n- Area: SDK\n- Names: `set_cwd`, `claim_session`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}