Adom Bridge

⋯ 1 unchanged line ⋯

@@ -1,6 +1,6 @@ {
   "slug": "adom-desktop",
-  "version": "1.9.95",
+  "version": "1.9.96",
   "type": "app",
   "description": "Laptop bridge: file transfer, screenshots, notifications, KiCad + Fusion 360 control, real-Chrome (Puppeteer) automation, and Hydrogen Desktop proxy. One install gives Claude every desktop verb it needs.",
   "discovery_pitch": "Use when a cloud AI needs to reach a real Windows desktop: run shell commands, capture screenshots, drive native apps and browsers, transfer files, and control KiCad / Fusion 360 / third-party bridges.",

@@ -1,6 +1,6 @@ {   "slug": "adom-desktop",-  "version": "1.9.95",+  "version": "1.9.96",   "type": "app",   "description": "Laptop bridge: file transfer, screenshots, notifications, KiCad + Fusion 360 control, real-Chrome (Puppeteer) automation, and Hydrogen Desktop proxy. One install gives Claude every desktop verb it needs.",   "keywords": [

@@ -1547,6 +1547,8 @@ Two ways to use it:  `screenRect` is in the SAME physical-px space as `desktop_list_windows` rects and the `desktop_click` default (`space:"screen"`). +> **Driving a GUI app that pops error boxes / modal dialogs? Read the dedicated [`adom-desktop-window-capture`](WINDOW_CAPTURE.md) skill.** `desktop_screenshot_window {hwnd}` captures ONE window AND the child dialogs / error boxes it owns, even when the window is backgrounded/occluded/minimized (PrintWindow, no focus steal). It is the breakthrough for automating native apps whose dialogs a full-screen grab can't see. The rest of this section is the reference; that skill is the how-and-why.+ **Popups (owned):** As of **v1.8.177**, `desktop_screenshot_window` **also captures the window's OWNED popups** — borderless confirm bubbles (Chromium's "Remove '\<ext\>'?"), owned dropdowns, owned dialogs — that don't enumerate in `desktop_list_windows` and aren't visible in a PrintWindow of the main window. They ride back as a top-level **`screenshots[]`** array (the same generic shape `kicad_screenshot_all` uses; the CLI auto-pulls each entry's `fullPath`→`localPath` and `safePath`→`localSafePath`). `ownedPopupCount` is always present (0 = none). Each entry carries `hwnd`, `title`, `kind:"owned_popup"`, and its own `coordMap`+`shotId`, so you can **click the bubble's buttons** with `{space:"image", shotId, x, y}` or drive them in the background by name via `desktop_ui_click {scope:"popups"}`. This is the generic mechanism — there's no app-specific "Chrome bubble" verb; every window screenshot surfaces any owned popups so you get the data and decide. **Use `desktop_screenshot_screen`** (full virtual-screen grab) only for popups *not owned* by your target window, or to see everything at once.  **Screen geometry on every shot (v1.8.178):** every `desktop_screenshot_window` / `_screen` response now carries:

@@ -1,12 +1,12 @@ {
   "manifest_version": 1,
-  "version": "1.9.95",
-  "released_at": "2026-07-06T00:00:00Z",
+  "version": "1.9.96",
+  "released_at": "2026-07-07T00:00:00Z",
   "windows": {
-    "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop/1.9.95/Adom.Desktop_1.9.95_windows_x64-setup.exe",
-    "installer_filename": "Adom.Desktop_1.9.95_windows_x64-setup.exe",
-    "installer_sha256": "523bd32f097febd554d7550c7d303730ae78a668ab8e65d00326dbcaacd92443",
-    "installer_size": 10415120
+    "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop/1.9.96/Adom.Desktop_1.9.96_windows_x64-setup.exe",
+    "installer_filename": "Adom.Desktop_1.9.96_windows_x64-setup.exe",
+    "installer_sha256": "128d075041f88b45fce2f625ca90116a7520f69c6e41da2c62b242d4f327476b",
+    "installer_size": 10414912
   },
   "changelog_url": "https://wiki.adom.inc/adom/adom-desktop",
   "minimum_required": "1.3.30",