{"version":"2.1.280","anchor":"device-revoked-session-message-removed-unified-unbound-sess","canonical_anchor":"device-revoked-session-message-removed-unified-unbound-sess","heading":"Device-revoked session message removed; unified unbound-session message used instead","tier":"notice","area":"Device Enrollment","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/device-revoked-session-message-removed-unified-unbound-sess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Device-revoked session message removed; unified unbound-session message used instead\n\nThe specific \"device removed from claude.ai\" explanation was dropped in favor of a generic unbound-session message\n\n**What**\n\nClaude Code previously showed a specific message when a machine had been removed from your claude.ai devices, explaining that it couldn't register again yet. That message has been removed. Now, that case falls through to the same generic message used for any unbound session: \"Start a new session to attach this machine; this one began unbound (no sync-back or local commands).\"\n\n**Why**\n\nA reader who sees this message after a device was revoked will get the generic wording rather than an explanation specific to device revocation.\n\n- Area: Device Enrollment\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}