{"version":"2.1.314","anchor":"oauth-login-error-can-be-shown-verbatim","canonical_anchor":"oauth-login-error-can-be-shown-verbatim","heading":"Login error screen can show a message without the OAuth error prefix","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/oauth-login-error-can-be-shown-verbatim","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Login error screen can show a message without the OAuth error prefix\n\nSome login errors now appear exactly as written, instead of always starting with \"OAuth error: \"\n\n**What**\n\nThe screen that appears when signing in fails always put \"OAuth error: \" in front of the message. OAuth is the sign-in method Claude Code uses with your account. Errors marked to be shown as written now appear exactly as written, with no prefix. All other errors still start with \"OAuth error: \".\n\n**Why**\n\nAn error that is not really a sign-in failure, such as one coming from a policy your organisation manages, no longer looks like an OAuth problem. That makes it clearer where to look for the cause.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}