Windows-to-Chrome session ownership, native placement and continuous human-view JPEG previews.
Users
5
+5 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#263K
#220K among extensions
Version
0.3.2
updated 22 Sep 2026
Users
monthly, 1 months
Latest, 18 Oct 2026:5 usersMove the mouse over the chart for any month
Ratings count
monthly, 1 months
Latest, 18 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About LazyChromeWindowBridge
LazyChromeWindowBridge is a developer companion extension for LazyChromeWindowBridge, not a standalone browser product. Installing this extension by itself does not provide a standalone dashboard or user workflow. It works only with a matching LazyChromeWindowBridge Windows/Core companion and authenticated owned sessions.
The Windows companion launches and owns Chrome windows. From the companion, developers can manage native window placement, PARK or RESTORE owned windows, monitor owned Visible or Parked windows through live JPEG previews, pause or resume monitoring for individual sessions, and adjust preview settings without changing the native browser window size.
Chrome may display its debugger notice while monitoring is enabled. The debugger API is used only for bounded functions required by the bridge: layout/screenshot capture and one structured allowlisted key/chord request to the exact owned active tab. Key dispatch uses fixed CDP Input.dispatchKeyEvent keyDown/keyUp operations. It is not arbitrary JavaScript, arbitrary CDP access, text macros, click automation, DOM automation, network inspection, or general remote-control functionality. Successful dispatch means the validated input request was sent; it does not guarantee that the webpage or Chrome UI handled the shortcut.
The bridge also observes Chrome Download Manager lifecycle notifications. These notifications are profile-wide and are not proof that a particular webpage produced a download. The extension does not start, cancel, pause, erase, open, or read downloads.
Absolute filenames and monitored page pixels can contain sensitive information. These are processed locally and sent only to the authenticated Windows companion on the same computer. There is no telemetry, advertising, analytics service, or cloud relay.
The extension does not inspect DOM content, run OCR, inspect network responses, infer webpage completion, record sessions, or discover and control arbitrary Chrome windows or tabs.
There is no toolbar popup. Use the LazyChromeWindowBridge Windows companion to operate the extension.
Requirements:
- Windows x64
- Chrome 120 or later
- Matching LazyChromeWindowBridge Core/Windows companion
Use matching Core and Extension versions. If the Chrome Web Store version temporarily lags the current GitHub/NuGet release, the matching extension ZIP is also available from the corresponding LazyChromeWindowBridge GitHub Release for Developer mode / Load unpacked installation.
Homepage:
https://github.com/Yasuhiko-m/LazyChromeWindowBridge
Support:
https://github.com/Yasuhiko-m/LazyChromeWindowBridge/issues
Privacy policy:
https://github.com/Yasuhiko-m/LazyChromeWindowBridge/blob/main/PRIVACY.md