{"version":"2.1.321","anchor":"auto-mode-refusal-messages-for-restricted-sessions","canonical_anchor":"auto-mode-refusal-messages-for-restricted-sessions","heading":"Clear reasons when a session can't run on this machine","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/auto-mode-refusal-messages-for-restricted-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Clear reasons when a session can't run on this machine\n\nClaude Code now explains why a session is refused with a \"Your session can't run on this machine\" message and a specific cause\n\n**What**\n\nWhen a session is refused, Claude Code now shows a message starting \"Your session can't run on this machine\" and names the cause. The causes are:\n\n- A gateway or custom endpoint is in use\n\n- Environment entries in the project change the model provider\n\n- No model usable in auto mode is available\n\n- An experimental-beta setting is turned off\n\n- A compliance policy\n\nA new check on `CLAUDE_CODE_USER_DELEGATED_SESSION_DIRECT_API` can lead to the reason that no allowed model is available.\n\n**Why**\n\nSessions that run for someone else or on hosted machines now get a specific reason when they are turned away, instead of failing without one.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}