{"version":"2.1.311","anchor":"mcp-tasks-oversized-status-answer-reported-as-answer-too-la","canonical_anchor":"mcp-tasks-oversized-status-answer-reported-as-answer-too-la","heading":"MCP tasks fail clearly when a status answer is too large","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/mcp-tasks-oversized-status-answer-reported-as-answer-too-la","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### MCP tasks fail clearly when a status answer is too large\n\nWhen an MCP task's status answer is too large to read, the task now fails with a message warning the tool may have run\n\n**What**\n\nSome MCP tools (tools added by add-on servers) run as longer tasks, and Claude Code repeatedly asks the server for their status. When a status answer is too large to read, or the connection closes for that reason, the task now fails with a clear message. The message says the answer was too large, that the tool may have run, and that Claude should ask for less data.\n\nBefore, this counted as an ordinary failed status check and Claude Code kept asking.\n\n**Why**\n\nThis stops Claude Code quietly asking again, or running a task again, when doing something twice could cause harm.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}