{"version":"2.1.280","anchor":"claude-in-chrome-tool-calls-now-surface-errors-instead-of-si","canonical_anchor":"claude-in-chrome-tool-calls-now-surface-errors-instead-of-si","heading":"claude-in-chrome tool calls now surface errors instead of silently returning undefined","tier":"notice","area":"Claude in Chrome","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/claude-in-chrome-tool-calls-now-surface-errors-instead-of-si","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### claude-in-chrome tool calls now surface errors instead of silently returning undefined\n\nclaude-in-chrome tool calls now throw a clear error on failure instead of silently returning nothing\n\n**What**\n\nWhen a claude-in-chrome MCP tool call fails, the code that unwraps its response now checks for an error flag and throws a proper error containing the tool's error text (or a generic \" failed\" message), instead of just returning undefined.\n\n**Why**\n\nPreviously a failed claude-in-chrome tool call could silently return nothing, making the failure hard to notice or diagnose. Now it surfaces as an explicit error with useful detail.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}