{"version":"2.1.247","anchor":"mcp-task-sidecars-on-a-newer-protocol-are-parked-instead-of-","canonical_anchor":"mcp-task-sidecars-on-a-newer-protocol-are-parked-instead-of-","heading":"MCP task sidecars on a newer protocol are parked instead of restored","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/mcp-task-sidecars-on-a-newer-protocol-are-parked-instead-of-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### MCP task sidecars on a newer protocol are parked instead of restored\n\nMCP helper processes declaring a newer protocol are parked on restore, awaiting a v2 runtime.\n\n**What**\n\nRestoring MCP task helper processes from a saved session now checks which protocol each one declared. Entries on the newer `sep2663` protocol are skipped by the older restore path with a log saying they need the v2 runtime.\n\n**Details**\n\n- Any protocol value that is not recognised is parked with an error-level log rather than restored blindly.\n- Both restore paths in the bundle carry the guard.\n\n**Evidence**\n\n`sep2663`\n\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}