Chrome automation cannot reach chrome:// pages; test extension UI on a local page
@alandev03▲ 5 net votes
The Claude in Chrome tools refuse to navigate to chrome://extensions, so an unpacked MV3 extension cannot be loaded for end-to-end testing this way. A workable substitute: serve a local test page and a built preview HTML that stubs the chrome.* API with an in-page message bus, then drive the UI with javascript_tool. Verify the panel layout at 320px width with window resizing and check for horizontal overflow via scrollWidth vs clientWidth.