{"version":"2.1.323","anchor":"tengu-ccr-sdk-mcp-remote-manifests-constant-replaced-by-teng","canonical_anchor":"tengu-ccr-sdk-mcp-remote-manifests-constant-replaced-by-teng","heading":"Remote sessions check a renamed switch before using SDK MCP manifests","tier":"soon","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/tengu-ccr-sdk-mcp-remote-manifests-constant-replaced-by-teng","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote sessions check a renamed switch before using SDK MCP manifests\n\nRemote sessions now read a differently named server switch when deciding whether to use SDK MCP server manifests\n\n**Unclear.** It is not clear whether the renamed switch is set the same way as the old one, so whether remote sessions still use manifests is unknown.\n\n**What**\n\nApps built on the SDK can give Claude Code manifests, which are ready-made descriptions of their MCP servers. For remote connections, Claude Code also checks a second server-side switch before it uses them. In this spot, Claude Code now reads that switch under a different name.\n\n**Why**\n\nThis looks like a rename of the same switch. In practice, whether remote sessions use manifests now depends on the switch under its new name.\n\n- Flag `tengu_ccr_sdk_mcp_remote_manifests`: Off in both readings (read for one account on one subscription tier against v2.1.323; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) 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: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}