{"version":"2.1.323","anchor":"mcp-sep2663-tasks-cannot-be-restored-in-compat-mode","canonical_anchor":"mcp-sep2663-tasks-cannot-be-restored-in-compat-mode","heading":"Some MCP tasks are set aside instead of restored in compat mode","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-sep2663-tasks-cannot-be-restored-in-compat-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Some MCP tasks are set aside instead of restored in compat mode\n\nIn compat mode, Claude Code no longer restores MCP tasks of one newer kind on resume and sets them aside as parked instead\n\n**Unclear.** What compat mode is and when Claude Code is in it is not known.\n\n**What**\n\nMCP (Model Context Protocol) servers are outside programs that give Claude Code extra tools. Some of them run long jobs, called tasks, that Claude Code checks on over time.\n\nWhen Claude Code restores these tasks, it now skips tasks of one newer kind while it is in compat mode. It logs that the task cannot be checked on in compat mode and has been parked, meaning set aside. Before, those tasks were always restored.\n\n**Why**\n\nThis affects picking up MCP tasks again when you resume work. In compat mode, a task of this kind is not followed up automatically.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}