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

John Lauer ·612582b49c ·3mo ago ·parent 305333e
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.122",
+  "version": "1.9.123",
   "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.122",+  "version": "1.9.123",   "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.122",+  "version": "1.9.123",   "released_at": "2026-07-15T00:00:00Z",   "windows": {-    "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop/1.9.122/Adom.Desktop_1.9.122_windows_x64-setup.exe",-    "installer_filename": "Adom.Desktop_1.9.122_windows_x64-setup.exe",-    "installer_sha256": "fe1d1f466dd649504250e8558ebcbeda981318cbaaa2cc84c0318daea527131f",-    "installer_size": 12766688+    "installer_url": "https://wiki.adom.inc/download/adom/adom-desktop/1.9.123/Adom.Desktop_1.9.123_windows_x64-setup.exe",+    "installer_filename": "Adom.Desktop_1.9.123_windows_x64-setup.exe",+    "installer_sha256": "d0db40e5cfb8271be9149172237b68e0c4616b4e14553952ba8e01a8c958a645",+    "installer_size": 12762680   },   "changelog_url": "https://wiki.adom.inc/adom/adom-desktop",   "minimum_required": "1.3.30",-  "note": "Multi-monitor screenshots reach the desktop correctly now: desktop_screenshot_screen takes {monitor:N} for one display or {perMonitor:true} for the stitched image plus a per-monitor image array (one image each, with physical/logical bounds and a coordMap). The v1.9.121 CLI was dropping these args; 1.9.122 forwards them. The default stitched all-monitors capture is unchanged. Also expanded the Notifications docs with every toast type, sample messages, and the response-tracking recipe."+  "note": "Fixes notify_user timing out when body is omitted (the normal shape for a progress-bar toast): the CLI sent a null body, the desktop rejected it in parsing, and the error was silently dropped so the caller just timed out. Progress toasts now work, title and body are optional, and a malformed notify returns a real error instead of hanging. The docs now show a live screenshot of every toast type next to the exact call that produced it, plus the response-tracking recipe (notify_response, notify_events, notify_dismiss)." }