Adom Bridge - Commit

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

Overview Files Skills Discover Packages Releases Dependencies Issues18 Breadcrumbs Pull Requests Activity

← Commit history

hd -> hydrogen prose; rename docs/adom-hydrogen.md

Kyle Bergstedt ·65d8e223ab ·2mo ago ·parent 34da380

1 file changed +1−1

docs/updates.md+1−1

@@ -12,7 +12,7 @@ When a newer version exists:  1. The signed installer (about 13 MB) is downloaded once and SHA256-verified against the manifest. 2. What happens next depends on your update mode (Settings, Updates): `prompt` (the default) shows a footer banner with Install now / Later; `auto` installs silently; `off` installs nothing.-3. The install runs the NSIS silently and relaunches the app. Since 1.9.175 that relaunch returns to the tray without showing or focusing the window, and when the machine is busy the auto-restart waits for about 15 minutes of idle time first (`update_idle_minutes`). Embedded under Hydrogen Desktop, AD stages the update and HD chooses the moment to apply it.+3. The install runs the NSIS silently and relaunches the app. Since 1.9.175 that relaunch returns to the tray without showing or focusing the window, and when the machine is busy the auto-restart waits for about 15 minutes of idle time first (`update_idle_minutes`). Embedded under Hydrogen Desktop, AD stages the update and Hydrogen chooses the moment to apply it.  Releases carry a priority tier. Normal releases (almost all of them) respect your mode. A high release auto-installs in the background even in `prompt` mode, with a toast saying so. An emergency release, reserved for a defect bad enough to pull from the whole fleet at once, shows a 60 second countdown and force-installs, and is additionally gated on the installer's Authenticode signature (it must be signed by Adom Industries) plus downgrade protection (only a strictly newer version can ever be forced). Even with updates set to `off` the 4-hour manifest check still runs, so an emergency signal can always reach the machine; `off` suppresses installs, not the check.