{"version":"2.1.281","anchor":"cd-drops-the-environment-block-is-stale-sentence-when-no","canonical_anchor":"cd-drops-the-environment-block-is-stale-sentence-when-no","heading":"Changing directory no longer calls the environment stale before any request was sent","tier":"notice","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cd-drops-the-environment-block-is-stale-sentence-when-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Changing directory no longer calls the environment stale before any request was sent\n\n\/cd and set_cwd now skip the 'environment block still names the previous directory' note when nothing has been sent to Claude yet\n\n**What**\n\nWhen you move a session to another folder with `\/cd`, or an app does so with the `set_cwd` control request, Claude receives a note about the move. The folder a session runs in is called its working directory.\n\n- The note's sentence \"The environment block at the start of this conversation still names the previous directory\" is now included only when a request has already been built, as reported by a new `requestBuilt` callback, or when no callback is given. One caller always reports that no request was built.\n\n- The result of the move now includes `freshSession`, which says whether the session was still fresh.\n\n- `set_cwd` passes `requestBuilt` in and receives `freshSession` back.\n\n**Why**\n\nBefore, the sentence was always included, so Claude could be told its starting information was out of date even though it had never been sent. Now Claude only gets that warning when it applies.\n\n- Area: Slash Commands\n- Names: `\/cd`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}