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.126

John Lauer ·f07453d0f6 ·3mo ago ·parent 83d9861
4 files changed +9−9
dist/linux/adom-desktoppackage.json+1−1page.json+1−1version.json+7−7
dist/linux/adom-desktop
⋯ 1 unchanged line ⋯
package.json+1−1
@@ -1,6 +1,6 @@ {
   "slug": "adom-desktop",
-  "version": "1.9.125",
+  "version": "1.9.126",
   "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.125",+  "version": "1.9.126",   "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+7−7
@@ -1,14 +1,14 @@ {   "manifest_version": 1,-  "version": "1.9.125",-  "released_at": "2026-07-15T00:00:00Z",+  "version": "1.9.126",+  "released_at": "2026-07-16T00:00:00Z",   "windows": {-    "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+    "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop/1.9.126/Adom.Desktop_1.9.126_windows_x64-setup.exe",+    "installer_filename": "Adom.Desktop_1.9.126_windows_x64-setup.exe",+    "installer_sha256": "4a28f913716f2801e5bc92d25c8d1c0a341b3f992720dd829ad246e273b00a3e",+    "installer_size": 12763368   },   "changelog_url": "https://wiki.adom.inc/adom/adom-desktop",   "minimum_required": "1.3.30",-  "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."+  "note": "Launch on boot now defaults ON and self-heals: AD recreates its Startup-folder shortcut on every launch if it goes missing (previously it was created only once during a version-upgrade window and never re-verified), so a fresh install reliably comes back after a reboot in both standalone and Hydrogen Desktop deployments. The Settings checkbox is checked by default and reflects the saved intent; unticking it removes the shortcut." }