{"version":"2.1.234","anchor":"wrong-account-device-token-now-gets-its-own-message","canonical_anchor":"wrong-account-device-token-now-gets-its-own-message","heading":"Wrong-account device token now gets its own message","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/wrong-account-device-token-now-gets-its-own-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Wrong-account device token now gets its own message\n\nA token from the wrong account now says so and tells you to log out.\n\n**What**\n\nDevice binding compares the stored account uuid against the host account uuid and reports a distinct mismatch failure telling you the token belongs to a different account and to run `claude \/logout`, rather than a generic binding error.\n\n**Details**\n\n- Adds an `account_mismatch` failure kind with its own explanation text.\n- A new `tengu_device_bind_account` event records which source the account uuid was read from.\n\n**Evidence**\n\n`the host's token is for a different account than this machine's (claude \/logout)`\n\n- Area: Auth\n- Names: `claude \/logout`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}