[BUG] Claude misinterprets the extension glow as an artifact

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?

I am using Claude Code to port designs between different frontend designs. My workflow is that I open up two tabs in chrome with the "master design" version (done by colleagues that iterate over designs in lovable) and another with the current codebase, and I basically tell claude to sync the two - along the lines of "take the version on tab 1 and sync it to tab 2, here is the symlink to the design implementation, etc".
Something that appears to happen is that when I tell it to sync colors, when it scans for certain areas in the screen (edges), it sees the actual extension orange glow that gets shown when the tab is active. This makes it misinterpret its own glow to be an artifact.

For the record, there is no "orange glow" in our designs. In fact, there is no orange at all.

What Should Happen?

Claude should not detect or see the glow at all and should see the actual design of the page, instead of manipulating it (I guess this is an extension design issue).

Error Messages/Logs

See screenshots

Steps to Reproduce

Tell claude to change a color of a component that falls under the glow edge and make it try to verify the color.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.75 (Claude Code)

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

Screenshots:
<img width="1912" height="698" alt="Image" src="https://github.com/user-attachments/assets/fc1d4160-069f-428c-b313-105d662df982" />

<img width="358" height="107" alt="Image" src="https://github.com/user-attachments/assets/4fa6652b-83dc-4a06-9ff6-22f81e4e457c" />