{"version":"2.1.283","anchor":"elicitation-response-notifications-no-longer-throw-on-failur","canonical_anchor":"elicitation-response-notifications-no-longer-throw-on-failur","heading":"Failed MCP input-response notifications no longer cause errors","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/elicitation-response-notifications-no-longer-throw-on-failur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Failed MCP input-response notifications no longer cause errors\n\nIf the notification sent after answering an MCP server's request for input fails, the error is now caught\n\n**What**\n\nMCP servers are external add-ons that give Claude Code extra tools, and they can ask you to fill something in. After you respond, Claude Code sends a notification. If that notification fails, the error is now caught, so it cannot break the handling of your response.\n\n**Why**\n\nThis prevents unhandled errors when an MCP server asks you for input.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}