{"version":"2.1.269","anchor":"new-403-error-message-for-device-bound-sessions-blocked-from","canonical_anchor":"new-403-error-message-for-device-bound-sessions-blocked-from","heading":"New 403 error message for device-bound sessions blocked from an unenrolled device","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-403-error-message-for-device-bound-sessions-blocked-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New 403 error message for device-bound sessions blocked from an unenrolled device\n\nNew clear error message when a device-bound session is blocked from an unenrolled device\n\n**What**\n\nSome sessions are bound to a specific device, so they only accept traffic from that device. When a request from a different device is blocked (an HTTP 403 error classified as \"bound_unattested\"), Claude Code now shows a specific message explaining this, instead of a generic HTTP error: the session accepts messages only from the device it's bound to, and suggests either sending from that device or running `\/login` to enroll the current one as a trusted device.\n\n**Why**\n\nThis turns a confusing generic error into an actionable one, telling you exactly why access was blocked and how to fix it by enrolling your current device with `\/login`.\n\n- Area: Auth\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}