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 Issues20 Breadcrumbs Pull Requests1 Activity
Closed general

Adom Bridge bundles adom-wiki 1.4.1 on Windows (current 1.7.63); it cannot run package install scripts

Colby Knox · 1mo ago ·closed by John Lauer

Adom Bridge on Windows ships adom-wiki.exe 1.4.1 at %LOCALAPPDATA%\Adom Bridge\adom-wiki.exe, and that copy is first on PATH. The current CLI is 1.7.63.

Two machines hit this on 2026-10-01: Aditya's, and Colby-ROG2 with Adom Bridge 2.1.163. On both, adom-wiki --version answered 1.4.1.

1.4.1 cannot install any package that has an install script on Windows. It hands bash a backslash path, and on a box where the first bash is WSL's launcher it fails before that. Each failure rolls the install back (adom/adom-wiki-cli#62, fixed in 1.7.63). Every other CLI fix since 1.4.1 is missing for these users too.

Asks:

  • Bundle the current adom-wiki, or fetch it at install and update time from https://wiki.adom.inc/download/adom/adom-wiki-cli/latest?platform=windows.
  • Or keep the bundled copy behind the user's own install on PATH.

1 Reply

John Lauer · 1mo ago

Fixed in 2.1.164 (insiders now).

Cause: the installer copies whatever adom-wiki the Adom Bridge build machine last compiled, and that checkout had stopped updating on 2026-08-11. So every installer since then shipped 1.4.1, first on PATH.

Fix:

  • 2.1.164 bundles adom-wiki 1.7.64, built from the v1.7.64 release tag and code-signed.
  • The release process now has a gate that refuses to ship when the bundled adom-wiki is older than the version download/adom/adom-wiki-cli/latest?platform=windows serves, or is unsigned. It fired on this very ship: 1.7.64 was published while 2.1.164 was building with 1.7.63, and the gate stopped it until the bundle was rebuilt.

Why I did not make Adom Bridge download adom-wiki at runtime: the published Windows adom-wiki-windows-x64.exe is unsigned, and an unsigned exe dropped into the install folder is exactly what Smart App Control blocks (#219). Bundling a signed copy each Adom Bridge release keeps it current without that risk. If adom-wiki-cli's own Windows releases get signed, a runtime refresh becomes safe.

Checked on arav-rog (2.1.164): %LOCALAPPDATA%\Adom Bridge\adom-wiki.exe is byte-for-byte the size of the signed 1.7.64 build (17,248,936).

John Lauer closed this · 1mo ago

Log in to reply.