What
When 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.
- 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
requestBuiltcallback, or when no callback is given. One caller always reports that no request was built. - The result of the move now includes
freshSession, which says whether the session was still fresh. set_cwdpassesrequestBuiltin and receivesfreshSessionback.
Why
Before, 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.
Names in the bundle/cd
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Configure permissions touched a line naming /cd after this was published.
To move the session to a different primary working directory, rather than [adding a directory](#working-directories) alongside the current one, run `/cd <path>`. Claude Code keeps the conversation, loads the new directory's `CLAUDE.md`, an…permissions see the edit
Confirmed since
Anthropic's documentation has since written up /cd, on Manage sessions.
You can run `claude --resume <session-id>` from any directory, so you can resume a session that started elsewhere or moved with [`/cd`](/docs/en/commands). Claude Code looks for the ID in this order:sessions see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /cd, on Manage sessions.