{"version":"2.1.287","anchor":"initialize-reply-waits-for-session-start-gated-by-tengu-ste","canonical_anchor":"initialize-reply-waits-for-session-start-gated-by-tengu-ste","heading":"Session startup reply now waits for start-up work to finish","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/initialize-reply-waits-for-session-start-gated-by-tengu-ste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Session startup reply now waits for start-up work to finish\n\nWhen a session is set up, Claude Code's first reply now waits, up to a limit, for the session's start-up work to finish\n\n**What**\n\nWhen 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.\n\nThis 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.\n\n**Why**\n\nThis 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.\n\n- Flag `tengu_steady_panda`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.287; this account: on, anonymous baseline: on, compiled default: 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.\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}