{"version":"2.1.274","anchor":"teleport-client-directory-sync-retraction-now-sends-a-truste","canonical_anchor":"teleport-client-directory-sync-retraction-now-sends-a-truste","heading":"Teleport client-directory-sync retraction now sends a trusted-device token","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/teleport-client-directory-sync-retraction-now-sends-a-truste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Teleport client-directory-sync retraction now sends a trusted-device token\n\nRetracting the Teleport client-directory-sync tag now sends a trusted-device token\n\n**Unclear.** Nothing has been read yet about the `tengu_teleport_client_directory_sync_retracted` gate, so it's unclear whether or how it governs this behavior.\n\n**What**\n\nWhen Claude Code retracts (undoes) its Teleport client-directory-sync tag, the request now also includes a `trustedDeviceToken` value, in addition to the parameters it already sent.\n\n**Why**\n\nIncluding a trusted-device token on this call lets the server verify the request is coming from a recognized device when the sync tag is being retracted.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}