When another program sets up a Claude Code session, Claude Code sends a first reply to confirm it is ready. That reply now waits for the session's start-up work to finish. The wait has a limit, and ends early if output is owed to the program that is reading.
This is behind the setting tengu_steady_panda. When the server sends nothing, the code treats it as on. In readings taken before this release, the flag server returned it as on for this site's account and for an anonymous check.
This changes the timing of the first reply, so a program driving Claude Code may see it arrive later but with start-up work already done.
tengu_steady_panda 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.287: 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.287. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_steady_panda