{"version":"2.1.300","anchor":"device-binding-failure-reason-for-console-profile-sign-ins","canonical_anchor":"device-binding-failure-reason-for-console-profile-sign-ins","heading":"Clearer reason when a Console sign-in can't be tied to a trusted device","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/device-binding-failure-reason-for-console-profile-sign-ins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Clearer reason when a Console sign-in can't be tied to a trusted device\n\nClaude Code explains that a Console-profile sign-in has no trusted-device token, because that token belongs to a claude.ai login\n\n**What**\n\nClaude Code can tie a session to a trusted device. When you are signed in with a Console profile, this cannot happen, and Claude Code now gives a reason: a Console-profile sign-in has no trusted-device token to bind with, because the token belongs to a claude.ai login.\n\n**Why**\n\nIf you sign in through the Console and see device binding skipped, the message tells you why.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}