{"version":"2.1.290","anchor":"chrome-tool-errors-now-carry-mcp-meta-and-an-error-source","canonical_anchor":"chrome-tool-errors-now-carry-mcp-meta-and-an-error-source","heading":"Claude in Chrome errors now pass along the tool's extra details","tier":"internal","area":"Chrome & Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/chrome-tool-errors-now-carry-mcp-meta-and-an-error-source","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Claude in Chrome errors now pass along the tool's extra details\n\nWhen a Claude in Chrome tool returns an error, the error now carries the result's _meta details and a label marking where it came from\n\n**Unclear.** It is not clear how the source label is used once the error is raised.\n\n**What**\n\nClaude in Chrome lets Claude work in your Chrome browser through tools. When one of those tools returns an error, the error Claude Code raises now carries the result's `_meta` field, a block of extra information, and is labelled as coming from an \"other\" source. It is also built as a different kind of error than before.\n\n**Why**\n\nFailures from Claude in Chrome tools can now be sorted by where they came from and keep their extra details for whatever handles them next.\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}