{"version":"2.1.277","anchor":"sdk-bridge-re-announce-now-also-reacts-to-mcp-command-list-c","canonical_anchor":"sdk-bridge-re-announce-now-also-reacts-to-mcp-command-list-c","heading":"SDK bridge re-announce now also reacts to MCP command-list changes","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/sdk-bridge-re-announce-now-also-reacts-to-mcp-command-list-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### SDK bridge re-announce now also reacts to MCP command-list changes\n\nSDK bridge now re-announces its init state when the list of MCP commands changes, not just model or permission settings\n\n**What**\n\nThe function that decides whether the SDK needs to re-send its 'system\/init' bridge announcement now also factors in the sorted list of non-terminal MCP command names, in addition to the model, permission mode, fast-mode, and effort settings it already checked.\n\n**Why**\n\nThis means that if the set of available MCP commands changes during a session, SDK-connected clients are now notified via a fresh announcement, keeping their view of available commands in sync.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}