{"version":"2.1.321","anchor":"auto-mode-notice-when-a-call-changed-after-review","canonical_anchor":"auto-mode-notice-when-a-call-changed-after-review","heading":"Auto mode explains when a call changed after review, including a restored working directory","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/auto-mode-notice-when-a-call-changed-after-review","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Auto mode explains when a call changed after review, including a restored working directory\n\nAuto mode now handles a new cd_restored rewrite cause and says when a call changed after it was reviewed\n\n**What**\n\nAuto mode is the mode in which Claude Code reviews tool calls itself instead of asking you before each one. A tool call is a single action Claude takes, such as running a command. Auto mode handles changes made to a call after review in two new ways:\n\n- A new message says that a call in the response \"changed (or may have changed) after auto mode reviewed it, so auto mode could not check what would run\".\n\n- A new rewrite cause, `cd_restored`, is treated like the `hook` and `tool_call_chain` rewrites. It covers the case where the working directory (the folder a command runs in) was restored after review.\n\n- The `cd_restored` cause carries the restored working directory and an `isRestoredCdGone` flag, and both are passed to the code that writes the deny message.\n\n**Why**\n\nWhen a call changes after auto mode has checked it, for example after a change of folder, auto mode now says why it could not check the call instead of leaving you to guess.\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"}