{"version":"2.1.323","anchor":"trusted-device-enrollment-can-use-host-cloud-sessions-token","canonical_anchor":"trusted-device-enrollment-can-use-host-cloud-sessions-token","heading":"Trusted-device setup can use a sign-in token from the host app","tier":"internal","area":"Trusted Devices","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/trusted-device-enrollment-can-use-host-cloud-sessions-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Trusted-device setup can use a sign-in token from the host app\n\nTrusted-device enrollment now waits for a cloud-sessions token from the host app instead of only using your sign-in token\n\n**What**\n\nEnrolling a trusted device registers the machine Claude Code runs on so it can be recognised. Before, enrollment used only your OAuth sign-in token. Now it can wait for a cloud-sessions token supplied by the host app that Claude Code runs inside.\n\nIf the sign-in ends while Claude Code is still waiting for that token, it skips enrollment and says so.\n\n**Why**\n\nThis lets enrollment work when Claude Code runs inside a hosted environment that provides its own sign-in.\n\n- Area: Trusted Devices\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}