SDK-registered in-process MCP servers can now skip a round-trip handshake at session start
A new sdkMcpServerManifests field on set_servers lets the host application pre-run an MCP server's own initialize and tools/list calls in-process and hand the results directly to the CLI. The CLI then uses those results to answer its own MCP client's handshake locally, instead of exchanging mcp_message control messages back and forth before the first turn.
Registering multiple in-process MCP servers this way costs no control-channel round trips before the first turn, which should make sessions with several SDK-provided MCP servers start faster.
tengu_sdk_mcp_manifests 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.265: on
Read once, for one account on one subscription tier, against v2.1.265. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
New in this build: tengu_sdk_mcp_manifests