{"version":"2.1.296","anchor":"auto-mode-unavailable-denial-now-shows-a-not-run-message","canonical_anchor":"auto-mode-unavailable-denial-now-shows-a-not-run-message","heading":"Actions skipped because auto mode got no answer now say \"Not run\"","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/auto-mode-unavailable-denial-now-shows-a-not-run-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Actions skipped because auto mode got no answer now say \"Not run\"\n\nWhen auto mode's check gives no usable answer, the skipped action now shows a dim \"Not run\" line saying so instead of a generic error\n\n**What**\n\nIn auto mode, Claude Code runs a check to decide whether an action can go ahead without asking you. When that check gives no usable answer and the action is stopped, Claude Code now shows a dim \"Not run\" line with the text \"auto mode's check had no usable answer\". Before, this case showed the same generic error display as any other failed tool call (a tool call is one action Claude takes, such as running a command or editing a file).\n\n**Why**\n\nYou can now tell that the action was never attempted because auto mode's check failed, rather than reading it as the action itself going wrong.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}