{"version":"2.1.319","anchor":"mcp-task-result-error-messages-are-logged","canonical_anchor":"mcp-task-result-error-messages-are-logged","heading":"Oversized MCP task results now log the reason they failed","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/mcp-task-result-error-messages-are-logged","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Oversized MCP task results now log the reason they failed\n\nWhen an MCP task's answer is too large, Claude Code now logs whether the size cap, Anthropic's MCP proxy or a closed connection was the cause\n\n**What**\n\nAn MCP server is a plugin-like service that gives Claude extra tools, and some of its work runs as tasks. When a task's answer is too large, Claude Code now writes a log line naming the cause:\n\n- the client's size cap\n\n- refusal by Anthropic's MCP proxy\n\n- a closed connection\n\nBefore, the error was returned with no log line.\n\n**Why**\n\nThis makes failed MCP tasks easier to diagnose.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}