Cloud sessions could delay starting language servers until needed, but the gate is off here.
Deferred LSP startup in cloud sessions is gated on tengu_moonlit_panda, off in this build.
tengu_moonlit_panda Gate removed from the codeThis release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
This account: on · anonymous baseline: on · compiled default in v2.1.246: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.246. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
In a cloud session, Claude Code can now skip starting its language server manager at launch, recording the context instead and starting it later if needed. This is decided by the gate tengu_moonlit_panda, which is off in this build, so absent a server-side value language servers start exactly as before.
- The deferral check applies only when the session looks remote:
CLAUDE_CODE_REMOTEset to true, or a remote session id, or a remote environment type. - The resolved gate value and its source are written to the log line
[LSP MANAGER] Remote session: tengu_moonlit_panda=. - The re-initialisation path was widened so a manager can still be created from the deferred state.
[LSP MANAGER] Remote session: tengu_moonlit_panda=, tengu_moonlit_panda
Strings lifted out of the shipped bundle, so the claim above can be checked against them.