{"version":"2.1.274","anchor":"oauth-failure-messages-during-tool-triggered-mcp-connect-now","canonical_anchor":"oauth-failure-messages-during-tool-triggered-mcp-connect-now","heading":"OAuth failure messages during tool-triggered MCP connect now include richer context","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/oauth-failure-messages-during-tool-triggered-mcp-connect-now","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### OAuth failure messages during tool-triggered MCP connect now include richer context\n\nOAuth failure messages from tool-triggered MCP connections now include richer context\n\n**What**\n\nWhen an OAuth authentication flow fails after being started by a tool call (for example, connecting to an MCP server), the error that gets logged and shown is now wrapped with additional context via a new helper before being reported, instead of showing the raw error text.\n\n**Why**\n\nThis should make failures during tool-triggered OAuth connections easier to diagnose, since the reported error carries more context about what triggered it.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}