{"version":"2.1.246","anchor":"groundwork-for-mcp-background-tasks-that-outlive-their-sessi","canonical_anchor":"groundwork-for-mcp-background-tasks-that-outlive-their-sessi","heading":"Groundwork for MCP background tasks that outlive their session","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/groundwork-for-mcp-background-tasks-that-outlive-their-sessi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Groundwork for MCP background tasks that outlive their session\n\nBackground MCP tasks could be parked and picked up by another session, but nothing creates them.\n\n**What**\n\nBackground MCP tasks gained a second protocol variant, named `sep2663`, whose tasks can be parked and handed to a helper process so another session can pick them up. Nothing in this build creates such a task, so none of these paths currently run.\n\n**Details**\n\n- The stored task record rejects an oversized task id for this variant on read.\n- The \"is this task still running\" check has a branch treating a parked task as owned by another session, by comparing the helper process's session id and project directory.\n- The kill path aborts the drive controller, calls the variant's cancel hook, then waits on the helper write and deletes the task metadata with helper arguments.\n- The only task constructor in the build accepts a protocol argument and its single caller does not pass one, and none of the helper fields or the parked flag are ever assigned, so every branch is unreachable.\n\n**Evidence**\n\n`sep2663 task id exceeds the wire bound`\n\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}