{"version":"2.1.290","anchor":"model-switch-validation-reports-sessionmoderefused-on-http-4","canonical_anchor":"model-switch-validation-reports-sessionmoderefused-on-http-4","heading":"Model switches can now be marked as refused because of the session's mode","tier":"internal","area":"Model Switching","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/model-switch-validation-reports-sessionmoderefused-on-http-4","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Model switches can now be marked as refused because of the session's mode\n\nWhen a model switch is rejected with a certain kind of 400 error, Claude Code now records it as a refusal tied to the session's mode\n\n**Unclear.** It is not clear which 400 errors count as a mode-based refusal.\n\n**What**\n\nBefore Claude Code switches you to a different model, it checks with the server that the switch is allowed. If the server answers with an HTTP 400 error (a response meaning the request was not accepted) of a particular kind, Claude Code now marks the result as a refusal caused by the session's mode, rather than treating it as an ordinary failure.\n\n**Why**\n\nThis lets Claude Code tell a refusal that comes from the mode your session is in apart from other errors that can happen while changing models.\n\n- Area: Model Switching\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}