app

Adom Bridge

Public Made by Adom

by adom

Adom Bridge unleashes your AI onto your full PC: full power, full safety. The AI breaks out of the container it runs in and onto your real machine, managing and running your entire laptop as you: launch apps, move files, drive any window, control KiCad, Fusion 360 or your real signed-in browser. Works with any AI, cloud or local (Claude Desktop, Claude Code, Codex), no Hydrogen required. Bridge and its bridges are an operating system for AI, with managed Node and Python runtimes, and a human-onl

adom-bridgetauriclaude-codebridgekicadfusion360puppeteerdesktop-automation
Overview Files Skills Discover Packages Releases Dependencies Issues19 Breadcrumbs Pull Requests1 Activity
← Commit history

Publish 1.9.125

John Lauer ·6591a85070 ·3mo ago ·parent 687ed1c
4 files changed +8−8
dist/linux/adom-desktoppackage.json+1−1page.json+1−1version.json+6−6
dist/linux/adom-desktop
⋯ 1 unchanged line ⋯
package.json+1−1
@@ -1,6 +1,6 @@ {
   "slug": "adom-desktop",
-  "version": "1.9.124",
+  "version": "1.9.125",
   "type": "app",
   "description": "Two parts, two machines. DOWNLOAD (below) = the Windows desktop APP — install it on the PC you want Claude to control (the bridge + GUI, signed, auto-updating). PKG INSTALL (this command) = for a cloud AI's Linux container/Docker — it drops the adom-desktop CLI + Claude skills there so an assistant can drive that Windows PC over the relay. You need the Download on your PC; you need the pkg only inside a container. Capabilities: file transfer, screenshots, notifications, KiCad + Fusion 360, real-Chrome (Puppeteer) automation, shell, windows, and Hydrogen Desktop proxy.",
   "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.",
page.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "adom-desktop",-  "version": "1.9.124",+  "version": "1.9.125",   "type": "app",   "description": "Two parts, two machines. DOWNLOAD (below) = the Windows desktop APP — install it on the PC you want Claude to control (the bridge + GUI, signed, auto-updating). PKG INSTALL (this command) = for a cloud AI's Linux container/Docker — it drops the adom-desktop CLI + Claude skills there so an assistant can drive that Windows PC over the relay. You need the Download on your PC; you need the pkg only inside a container. Capabilities: file transfer, screenshots, notifications, KiCad + Fusion 360, real-Chrome (Puppeteer) automation, shell, windows, and Hydrogen Desktop proxy.",   "keywords": [
version.json+6−6
@@ -1,14 +1,14 @@ {   "manifest_version": 1,-  "version": "1.9.124",+  "version": "1.9.125",   "released_at": "2026-07-15T00:00:00Z",   "windows": {-    "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop/1.9.124/Adom.Desktop_1.9.124_windows_x64-setup.exe",-    "installer_filename": "Adom.Desktop_1.9.124_windows_x64-setup.exe",-    "installer_sha256": "52ccb8ca9f8ee0a93146438fbd4af57c66179e71d63d3aa2e970680a434977f9",-    "installer_size": 12764592+    "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop/1.9.125/Adom.Desktop_1.9.125_windows_x64-setup.exe",+    "installer_filename": "Adom.Desktop_1.9.125_windows_x64-setup.exe",+    "installer_sha256": "05de062fbb485f0fda3b978703fdae63b1627a247f908d9f4cd1f70f74db3cc0",+    "installer_size": 12769672   },   "changelog_url": "https://wiki.adom.inc/adom/adom-desktop",   "minimum_required": "1.3.30",-  "note": "Security/policy fix (bridge issue 163): browser_raise_os_window is no longer intercepted by AD-core. It now routes to the puppeteer bridge like every other browser_ verb, so the bridge's foreground gate applies: raising a pup window onto your screen requires a stated reason (foregroundReason), which is logged and surfaced as lastForeground in browser_status. Previously any cloud thread could raise a pup window silently with no audit trail. desktop_bring_to_front remains AD's own native raise for any non-pup window."+  "note": "Taskbar icon polish: the per-window RelaunchIconResource shell property is now kept in sync with the applied variant in BOTH standalone and embedded modes (previously set for standalone only, pointing at the wrong-color icon), so a window that flips between standalone and embedded can never shadow its recreated taskbar button with the wrong tile. Standalone stays the muted teal; embedded (Hydrogen Desktop driving) stays the vivid teal." }