{"version":"2.1.281","anchor":"trusted-device-enrollment-reports-why-it-did-not-bind","canonical_anchor":"trusted-device-enrollment-reports-why-it-did-not-bind","heading":"Trusted-device enrollment reports why it did not bind","tier":"internal","area":"Auth","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/trusted-device-enrollment-reports-why-it-did-not-bind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Trusted-device enrollment reports why it did not bind\n\nTrusted-device enrollment now reports a reason when a device is not bound, such as trusted_devices_off or enrollment_paused\n\n**Unclear.** The finding does not say where, or whether, these reasons are shown to the person using Claude Code.\n\n**What**\n\nThe step that enrolls, or binds, a device as trusted to your account now returns a reason when the binding does not happen. The reasons include:\n\n- `trusted_devices_off`\n\n- `enrollment_paused`\n\n- `not_given`\n\n**Why**\n\nBefore this, a device that failed to bind gave no stated cause. A named reason makes it possible to tell a switched-off feature apart from a paused enrollment or a missing input.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}