[BUG] Claude in Chrome extension causes persistent yellow screen border on all monitors (Windows)
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?
After using Claude Code with the Claude in Chrome extension, a persistent yellow border appeared around the edge of all three of my monitors. This is the Windows "screen capture active" indicator that appears when an application is using the Windows Graphics Capture API.
The border persisted even after:
- Closing Chrome completely
- Killing DWM (Desktop Window Manager)
- Restarting the graphics driver (Win+Ctrl+Shift+B)
- Killing all RuntimeBroker processes
Only a full system restart cleared the border.
Windows Event Viewer logged the following at the time the border appeared:
Event: WindowsBlackScreenDiagnosticsV1
P1: DWM
P3: ColorBits
P4: Hotkey
This suggests the Chrome extension's screen capture functionality (used for screenshots/GIF recording) did not properly release its capture session, leaving Windows stuck in a "capture active" state.
What Should Happen?
Screen capture sessions initiated by the Chrome extension should be properly released/terminated when:
- The browser tab or window is closed
- The extension disconnects from Claude Code
- The Claude Code session ends
- Chrome is closed
The Windows screen capture indicator should not persist after the capture operation completes or the application closes.
Error Messages/Logs
From Windows Event Viewer (Application Log):
TimeCreated: 2026-02-03 11:29:14 AM
ProviderName: Windows Error Reporting
Event Name: WindowsBlackScreenDiagnosticsV1
Problem signature:
P1: DWM
P2: Unknown
P3: ColorBits
P4: Hotkey
P5: 10.0.19041.6807
Steps to Reproduce
Steps to Reproduce
- Launch Claude Code with the Claude in Chrome MCP extension enabled
- Use the browser automation tools (exact trigger uncertain - possibly screenshot or GIF recording functionality)
- Close Chrome or disconnect the extension
- Observe: Yellow border remains around all monitors
- Attempt standard fixes (restart DWM, graphics driver, kill RuntimeBroker) - border persists
- Only full system restart clears the border
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
Not sure last stable
Claude Code Version
2.1.30 Claude Code
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
- Multi-monitor setup: 3 displays
- The yellow border is the Windows privacy indicator shown when apps use the Windows.Graphics.Capture API
- Color Filters in Windows Settings confirmed OFF (not the cause)
- The "Hotkey" value in the Windows event log is puzzling since no keyboard shortcut was deliberately pressed - suggests the extension may have programmatically triggered something
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗