{"version":"2.1.301","anchor":"gettask-handles-output-from-tasks-running-elsewhere-sdk-mcp","canonical_anchor":"gettask-handles-output-from-tasks-running-elsewhere-sdk-mcp","heading":"Tasks running elsewhere get their output handled differently; SDK MCP servers lose tools field","tier":"internal","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/gettask-handles-output-from-tasks-running-elsewhere-sdk-mcp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Tasks running elsewhere get their output handled differently; SDK MCP servers lose tools field\n\nBackground tasks marked as running elsewhere now report a rewritten output path and a final response, and SDK-type MCP configs drop their tools list\n\n**Unclear.** Which tasks count as running elsewhere is not stated.\n\n**What**\n\nA background task is a job Claude Code runs while you keep working. When Claude Code takes a snapshot of such a task and the task is marked as running elsewhere, it now:\n\n- rewrites the path of the task's output file\n\n- treats the task's output as its final response\n\nSeparately, for MCP servers (add-on programs that give Claude Code extra tools) of type `sdk`, Claude Code now drops the `tools` field from the server's configuration.\n\n**Why**\n\nThese are small fixes in how remote tasks and SDK MCP servers are handled.\n\n- Area: Background Shells\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}