{"version":"2.1.304","anchor":"auth-trusted-device-refusal-message-and-api-error-classific","canonical_anchor":"auth-trusted-device-refusal-message-and-api-error-classific","heading":"Sign-in errors are sorted more precisely, and the trusted-device message varies","tier":"notice","area":"Auth","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/auth-trusted-device-refusal-message-and-api-error-classific","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Sign-in errors are sorted more precisely, and the trusted-device message varies\n\nUnexplained sign-in errors are now sorted into more specific kinds, and the trusted-device refusal message depends on whether you just enrolled\n\n**What**\n\nThe message shown when sign-in is refused because the device is not trusted now depends on whether the device was just enrolled.\n\nUnknown errors from Anthropic's servers are also sorted more precisely:\n\n- A 304 reply (an HTTP status meaning \"not modified\") is now treated as blocked by something in between, such as a proxy.\n\n- Other unknown errors are now treated as being unable to connect or as a client error.\n\nBefore, all of them counted as a general client error.\n\n**Why**\n\nErrors are labelled more accurately in messages and in what Claude Code records. A problem caused by something between you and Anthropic can be told apart from an ordinary failure.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}