{"version":"2.1.321","anchor":"hybrid-only-sign-in-tracked-in-login-reuse-check","canonical_anchor":"hybrid-only-sign-in-tracked-in-login-reuse-check","heading":"Sign-in reuse now also checks for a hybrid-only sign-in","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/hybrid-only-sign-in-tracked-in-login-reuse-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Sign-in reuse now also checks for a hybrid-only sign-in\n\nBefore reusing a sign-in that is already in progress, Claude Code now also checks whether it is a hybrid-only sign-in\n\n**Unclear.** What a hybrid-only sign-in is, and whether a reader can use it yet, is not stated.\n\n**What**\n\nWhen you start signing in while another sign-in is already under way, Claude Code decides whether it can reuse the one in progress. That decision used to compare only whether both use a Claude.ai login and which organisation they belong to. It now also compares whether each one is a hybrid-only sign-in.\n\n**Why**\n\nIt points to a separate hybrid-only way of signing in, which is now kept apart from other sign-ins when deciding what can be reused.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}