{"version":"2.1.319","anchor":"navigation-errors-classified-into-error-types","canonical_anchor":"navigation-errors-classified-into-error-types","heading":"Browser tool errors are sorted into more specific error types","tier":"notice","area":"Claude in Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/navigation-errors-classified-into-error-types","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Browser tool errors are sorted into more specific error types\n\nErrors from Claude's Chrome browser tool are now matched to named types such as tab_not_found, with broader patterns for tab and security-check errors\n\n**Unclear.** It is not clear whether these kinds are ever shown to you or are only recorded inside Claude Code.\n\n**What**\n\nClaude Code has a browser tool that lets Claude drive Chrome. When one of its actions fails, Claude Code now compares the error message against a table of patterns and gives the error a named type. Before, a simple yes-or-no helper handled this.\n\n- `navigate_permission_denied`, `navigate_beforeunload_blocked`, `tab_not_found` and `navigate_exception` are the new types for errors when opening a page.\n\n- `tab_not_found` now also matches a tab that \"is not in Claude's tab group for this session\", meaning a tab outside the group of tabs Claude is using for the current run.\n\n- `security_check_failed` now matches any \"Security check failed\" message and any \"Origin mismatch:\" message. Before, it matched only a security check failing because the domain changed, or Claude Code being unable to verify the current address for the check.\n\n**Why**\n\nIn practice, more browser tool failures are recorded under a specific type instead of a vague one, so a failed page load, a missing tab and a failed security check are told apart.\n\n- Area: Claude in Chrome\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}