{"version":"2.1.238","anchor":"mcp-instruction-blocks-re-emit-when-a-server-s-instructions-","canonical_anchor":"mcp-instruction-blocks-re-emit-when-a-server-s-instructions-","heading":"MCP instruction blocks re-emit when a server's instructions change","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/mcp-instruction-blocks-re-emit-when-a-server-s-instructions-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### MCP instruction blocks re-emit when a server's instructions change\n\nChanged MCP server instructions would be re-sent instead of suppressed, but that needs the disabled discovery cache.\n\n**What**\n\nThe record of MCP server instructions now keeps each server's own instruction text next to the rendered block, so a still-connected server whose instructions changed gets its block re-sent instead of suppressed as already present. Re-emitting on change requires the MCP discovery cache, which is not enabled by default.\n\n**Evidence**\n\n`tengu_mcp_instructions_pool_change`\n\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}