[Bug] Chrome browser validation failing: MCP integration broken, auto-launch disabled, Playwright MCP not functioning

Resolved 💬 3 comments Opened Jan 16, 2026 by tomaslucas Closed Jan 20, 2026

Bug Description
The use of Chrome for validation is not working well. Before, I could use it without problems, but now it doesn't manage to do the minimum requested work. Before, it would open Chrome if it wasn't open, now it just complains - I have to open it myself, and if there's another window it gets confused. Before, Claude appeared in the tab group, now it shows Claude (MCP). Before, I could ask it to use Playwright's MCP instead of Claude, now it doesn't handle it well. To verify, since I've performed this operation several times before, I've tested with Ampcode and Playwright's MCP and it works without problems.

Environment Info

  • Platform: linux
  • Terminal: WarpTerminal
  • Version: 2.1.9
  • Feedback ID: d76d1eb0-877a-41ca-bda4-35ceb8b0e5c0

Errors

[{"error":"Error: Error clicking: Cannot access a chrome-extension:// URL of different extension\n    at YvI (/$bunfs/root/claude:1277:16836)\n    at async call (/$bunfs/root/claude:1277:30364)\n    at async Mp9 (/$bunfs/root/claude:2715:19646)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-01-16T11:09:43.838Z"},{"error":"Error: Error capturing screenshot: Cannot access a chrome-extension:// URL of different extension\n    at YvI (/$bunfs/root/claude:1277:16836)\n    at async call (/$bunfs/root/claude:1277:30364)\n    at async Mp9 (/$bunfs/root/claude:2715:19646)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-01-16T11:09:50.400Z"},{"error":"Error: Failed to execute JavaScript: Cannot access a chrome-extension:// URL of different extension\n    at YvI (/$bunfs/root/claude:1277:16836)\n    at async call (/$bunfs/root/claude:1277:30364)\n    at async Mp9 (/$bunfs/root/claude:2715:19646)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-01-16T11:09:59.357Z"},{"error":"Error: No element found with reference: \"ref_13\". The element may have been removed from the page.\n    at YvI (/$bunfs/root/claude:1277:16836)\n    at async call (/$bunfs/root/claude:1277:30364)\n    at async Mp9 (/$bunfs/root/claude:2715:19646)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-01-16T11:10:14.172Z"},{"error":"Error: No element found with reference: \"ref_15\". The element may have been removed from the page.\n    at YvI (/$bunfs/root/claude:1277:16836)\n    at async call (/$bunfs/root/claude:1277:30364)\n    at async Mp9 (/$bunfs/root/claude:2715:19646)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-01-16T11:10:14.226Z"},{"error":"Error: Error clicking: Cannot access a chrome-extension:// URL of different extension\n    at YvI (/$bunfs/root/claude:1277:16836)\n    at async call (/$bunfs/root/claude:1277:30364)\n    at async Mp9 (/$bunfs/root/claude:2715:19646)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-01-16T11:10:30.712Z"},{"error":"Error: Error capturing screenshot: Cannot access a chrome-extension:// URL of different extension\n    at YvI (/$bunfs/root/claude:1277:16836)\n    at async call (/$bunfs/root/claude:1277:30364)\n    at async Mp9 (/$bunfs/root/claude:2715:19646)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-01-16T11:10:35.318Z"}]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗