{"version":"2.1.321","anchor":"auto-mode-gives-a-new-refusal-when-no-allowed-model-can-run","canonical_anchor":"auto-mode-gives-a-new-refusal-when-no-allowed-model-can-run","heading":"Auto mode explains when no allowed model can check an action","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/auto-mode-gives-a-new-refusal-when-no-allowed-model-can-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Auto mode explains when no allowed model can check an action\n\nAuto mode now refuses an action with a clear message when none of the models allowed to check it can be used\n\n**What**\n\nIn auto mode, Claude Code has a model check each action before it runs. There is now a separate reason for when that check cannot happen: none of the models allowed to check this session's actions can be used here. In that case the tool is not run, and Claude is told to stop and tell you. This reason is connected to the `CLAUDE_CODE_USER_DELEGATED_SESSION_DIRECT_API` environment variable.\n\n**Why**\n\nOn setups where only certain models may be used, auto mode can now say why it blocked an action instead of failing without a clear reason.\n\n- Area: Auto Mode\n- Names: `CLAUDE_CODE_USER_DELEGATED_SESSION_DIRECT_API`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}