{"version":"2.1.319","anchor":"gettask-refusal-text-and-image-stripping-from-completed-task","canonical_anchor":"gettask-refusal-text-and-image-stripping-from-completed-task","heading":"Finished MCP task results have images replaced with \"[image]\"","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/gettask-refusal-text-and-image-stripping-from-completed-task","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Finished MCP task results have images replaced with \"[image]\"\n\nClaude now sees \"[image]\" in place of images in finished MCP task results, and the GetTask refusal mentions tasks as well as background commands\n\n**What**\n\nTwo changes affect what Claude sees about background work.\n\n- When Claude tries to call `GetTask` and is told there is no such tool, the message now says \"A background command's or task's result reaches you by itself when it finishes\". It used to mention only background commands.\n\n- When a task run through an MCP server (an add-on that gives Claude Code extra tools) finishes, any image in its saved result is replaced with the text \"[image]\".\n\n**Why**\n\nClaude is told more clearly that it does not need to ask for task results, because they arrive on their own. Images inside a finished MCP task's result will no longer reach Claude as images, only as a placeholder.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}