{"version":"2.1.281","anchor":"credentials-changed-on-disk-event-helper","canonical_anchor":"new-sibling-login-watch-picks-up-a-login-made-in-another-cla","heading":"A login in another Claude Code window now clears the login notice here","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/credentials-changed-on-disk-event-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### A login in another Claude Code window now clears the login notice here\n\nSessions stuck at the login notice now notice when you log in from another Claude Code process and clear themselves\n\n**Unclear.** The finding does not say what Claude Code does after the `credentialsChangedOnDisk` event is sent.\n\n**What**\n\nIf a Claude Code session is showing the login notice (because your credentials are missing or invalid) and you log in with `\/login` in another Claude Code window or terminal, the waiting session can now pick up that login by itself:\n\n- The credentials cache gains a `credentialsChangedOnDisk` event, fired when the credentials file changes on disk, and a `lastOwnSavedAccessToken` field recording the token this process saved itself.\n\n- When a session starts, the SessionController calls `_startSiblingLoginWatch`, which listens for that event. When it fires, `_adoptSiblingLogin` runs `apiKeyVerification.recheckAfterCredentialsChange`, with `_scheduleSiblingLoginCheck` also involved.\n\n- The recheck only runs while the login notice is showing (`missing` or `invalid`), and it skips tokens this process saved itself by comparing against `lastOwnSavedAccessToken`.\n\n- If the new credentials check out, the session refreshes managed settings (settings your organization controls) and marks the login complete.\n\n- If that refresh does not finish, a warning is logged that claude.ai connectors and other login-dependent features stay as they were until `\/login` or a restart.\n\nNothing has been read about the `tengu_streamed_thimble` gate, so its state is unknown.\n\n**Why**\n\nBefore, a 'please log in' notice could stay on screen in one session after you had already logged in from another. Now that session can clear the notice without a restart. If you see the warning above, run `\/login` or restart to get connectors working with the new login.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}