Unclear It is not clear whether this behaves any differently from the previous build.
Claude Code signs subscription accounts in with a token, a saved credential that expires and has to be refreshed. While it refreshes, Claude Code holds a lock, a marker that stops two refreshes running at once. If you use a subscription, the wait for that lock times out, and your token has already expired, Claude Code stops with a dedicated error for that situation.
This check sits behind a server-controlled switch named tengu_sharded_beacon. When the server sends nothing, the switch counts as on.
The check looks the same as in the previous build, apart from internal renaming, so there may be no difference in what you see. If you do hit this error, it means the refresh could not finish in time and your saved sign-in had already expired.
tengu_sharded_beacon On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.290: 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.290. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear whether this behaves any differently from the previous build.