{"version":"2.1.311","anchor":"bash-tool-description-now-says-when-cd-carries-over","canonical_anchor":"bash-tool-description-now-says-when-cd-carries-over","heading":"Bash tool instructions now spell out when cd carries over","tier":"notice","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/bash-tool-description-now-says-when-cd-carries-over","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Bash tool instructions now spell out when cd carries over\n\nClaude's Bash tool instructions now say `cd` carries to the next command only in the main session, after success, inside the working directories\n\n**What**\n\nThe Bash tool lets Claude run shell commands. Its description, the instructions Claude reads about the tool, has a rewritten line about the working directory. The line is now built by the program instead of being fixed text. The rewrite was captured under this release and appears in the `agent-claude`, `compaction`, `command-init` and `command-security-review` prompts.\n\n- `cd` carries to the next call only in the main session, if the command succeeds and ends inside the working directories.\n\n- Outside them the shell returns to the start folder; otherwise it stays where it was.\n\n- Shell state does not persist. The shell environment is initialized from the user's profile (bash or zsh).\n\nThe old line said only that the working directory persists between calls, that absolute paths are preferred, and that `cd` in a compound command can trigger a permission prompt.\n\n**Why**\n\nClaude now has an exact rule for when a change of folder sticks. In subagents, which are helper agents Claude starts for a task, after a failed command, or after leaving your project folders, the next command starts from the original folder.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}