{"version":"2.1.269","anchor":"new-device-registration-failure-reason-no-login-keychain","canonical_anchor":"new-device-registration-failure-reason-no-login-keychain","heading":"New device-registration failure reason: no login keychain","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-device-registration-failure-reason-no-login-keychain","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New device-registration failure reason: no login keychain\n\nDevice registration on Mac now reports a clear error when there's no login keychain to store a device key\n\n**What**\n\nWhen Claude Code tries to register (bind) a device and the Mac user account has no login keychain available to store a device key in, it now surfaces this as its own distinct failure reason, `no_keychain`, with a specific user-facing message explaining the problem. Separately, untrusted-device errors gained a new sub-reason, `bound_unattested`.\n\n**Why**\n\nThis gives a clearer, more specific error message when device binding fails because of a missing keychain, instead of a generic or confusing failure.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}