[BUG] Claude in Chrome extension opens 4 broken tabs (native/host/wrapper/script) with DNS_PROBE_FINISHED_NXDOMAIN

Status Open
Reported on v2.1.217
Maintainer reply None cached
Activity 1 comment · opened Jul 21, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude in Chrome extension (v1.0.81) opens 4 extra broken tabs — native, host, wrapper, script — whenever a new tab is opened via a local script. Each new tab's address bar shows only the bare word (e.g. script/) and fails with DNS_PROBE_FINISHED_NXDOMAIN.

What Should Happen?

No extra tabs should open. Only the intended tab (e.g. https://x.com/compose/post) should open.

Error Messages/Logs

No console errors captured. Each broken tab shows Chrome's built-in error page: DNS_PROBE_FINISHED_NXDOMAIN

Steps to Reproduce

  1. Ensure the Claude in Chrome extension (v1.0.81) is enabled
  2. From a local script, open a new browser tab via PowerShell:

Start-Process "https://x.com/compose/post"

  1. Observe that in addition to the intended tab, 4 extra tabs open automatically: native, host, wrapper, script
  2. Each new tab's address bar shows only the bare word (e.g. script/), and fails with DNS_PROBE_FINISHED_NXDOMAIN

Isolation testing:

  • Extensions with site access to x.com: Adobe Acrobat, Claude, Stella Browser for Biz
  • Disabling Stella Browser for Biz only → issue still occurred
  • Additionally disabling Claude in Chrome (Adobe Acrobat still enabled) → issue stopped occurring
  • This isolates the cause to the Claude in Chrome extension

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.217 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗