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
credentialsChangedOnDiskevent, fired when the credentials file changes on disk, and alastOwnSavedAccessTokenfield recording the token this process saved itself. - When a session starts, the SessionController calls
_startSiblingLoginWatch, which listens for that event. When it fires,_adoptSiblingLoginrunsapiKeyVerification.recheckAfterCredentialsChange, with_scheduleSiblingLoginCheckalso involved. - The recheck only runs while the login notice is showing (
missingorinvalid), and it skips tokens this process saved itself by comparing againstlastOwnSavedAccessToken. - 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
/loginor 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.
tengu_streamed_thimble Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.281: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.281. It isn't a statement about your account. What a flag value here can and cannot tell you
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
With `awsAuthRefresh` configured, run `/login`, select **3rd-party platform**, then select **Claude Platform on AWS · refresh credentials** under **Using 3rd-party platforms**. Claude Code runs the configured command and re-reads your AWS …claude-platform-on-aws see the edit
| [Login enforcement](/docs/en/settings-reference#forceloginmethod) | Restrict login to a specific method or Anthropic organization. The method restriction applies across the VS Code extension, Agent SDK, `claude setup-token`, and `/instal…admin-setup see the edit
The finding names `tengu_streamed_thimble` but does not say whether that gate controls this watch.
Anthropic's documentation has since written up /login, on Set up Claude Code for your organization.
Added telemetry.resource_attributes to the Claude apps gateway config, to put fixed labels on the telemetry of Claude Desktop and /login…
New in this build: tengu_streamed_thimble