{"version":"2.1.269","anchor":"device-attestation-retry-path-added-for-session-event-delive","canonical_anchor":"device-attestation-retry-path-added-for-session-event-delive","heading":"Device-attestation retry path added for session event delivery","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/device-attestation-retry-path-added-for-session-event-delive","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Device-attestation retry path added for session event delivery\n\nSession events refused with a 403 can now be re-signed by the device and resent instead of dropped\n\n**What**\n\nWhen Claude Code tries to send a session event (a record of activity in your session) to the server and gets back an HTTP 403 (permission refused) response, it can now, if a related setting is enabled, work out why: whether the device is unattested (not verified) or the session login has gone stale. In either case, it re-signs the event using a device signer and resends it, logging the message \"Refused unsigned by a session bound to this machine; resending signed.\"\n\n**Why**\n\nThis lets session activity get through even when a device-bound session initially rejects it for lacking a valid signature, instead of the event being silently lost.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}