A login in another Claude Code window now clears the login notice here

What

If 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:

• 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.
• When a session starts, the SessionController calls _startSiblingLoginWatch, which listens for that event. When it fires, _adoptSiblingLogin runs apiKeyVerification.recheckAfterCredentialsChange, with _scheduleSiblingLoginCheck also involved.
• 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.
• If the new credentials check out, the session refreshes managed settings (settings your organization controls) and marks the login complete.
• 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.

Nothing has been read about the tengu_streamed_thimble gate, so its state is unknown.

Why

Before, 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.