{"version":"2.1.321","anchor":"auto-mode-handles-bash-calls-whose-leading-cd-was-rewritten","canonical_anchor":"auto-mode-handles-bash-calls-whose-leading-cd-was-rewritten","heading":"Auto mode gives clearer answers when a command's leading cd no longer matches","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/auto-mode-handles-bash-calls-whose-leading-cd-was-rewritten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Auto mode gives clearer answers when a command's leading cd no longer matches\n\nWhen auto mode checked a shell command without its leading cd and the folder has since changed, Claude is told how to retry\n\n**What**\n\nIn auto mode, Claude Code reviews shell commands before running them. Sometimes a command starts with `cd` (change folder), and the review looked at the command without that part. If the shell's current folder has moved since, the review no longer covers what would actually run.\n\nClaude Code now handles two cases:\n\n- The shell has moved: the refusal tells Claude to send the command again with its original wording.\n\n- The `cd` target no longer exists: the message says the command was not run because it would fail.\n\n**Why**\n\nClaude gets a clear next step instead of hitting a refusal it cannot get past, so fewer auto-mode runs stall after the working folder changes.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}