{"version":"2.1.285","anchor":"mcp-background-tasks-sep2663-merge-follow-up-messages-and","canonical_anchor":"mcp-background-tasks-sep2663-merge-follow-up-messages-and","heading":"MCP tasks can run in the background and accept follow-up messages","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/mcp-background-tasks-sep2663-merge-follow-up-messages-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### MCP tasks can run in the background and accept follow-up messages\n\nBackground MCP tasks can take a follow-up message mid-run, and a crashed one is reported as failed with the code drive_crashed\n\n**Unclear.** It is not clear what switches this on or whether it is reachable yet.\n\n**What**\n\nMCP servers are external tools Claude Code can connect to. Claude Code can now keep track of tasks from those servers that run in the background, meaning they keep working while you carry on. Each background task has its own separate record.\n\n- Follow-up messages: a message you send can be merged into a background task that is still running, instead of waiting for it to finish.\n\n- Crashes: if the process running a background task stops unexpectedly, the task is marked as failed with the code `drive_crashed`.\n\n**Why**\n\nThis is the first groundwork for MCP tasks that run in the background. When one crashes, it is reported as failed rather than left looking unfinished.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 5\/5\n- Signal: 4\/5"}