sync_skills installs nothing on Windows (install.sh path mangled through bash) — the bridge-skill half of verb discovery - Adom Bridge

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 Issues19 Breadcrumbs Pull Requests1 Activity

Closed bug report

sync_skills installs nothing on Windows (install.sh path mangled through bash) — the bridge-skill half of verb discovery

John Lauer · 1mo ago ·closed by John Lauer

Found while fleet-testing #212 on 2026-09-22 (ab 2.1.148 on arav-rog). Not caused by that work; sync_skills has been untouched through the whole series.

sync_skills is how an AI gets each installed bridge's own how-to, which matters more now that ab carries no bridge documentation at all (#211/#212). It fails on both places I can run it:

On Windows (arav-rog, bundled adom-wiki 1.4.1): 6 of 6 bridges fail with

/bin/bash: C:Usersaravprojectadom_modulesadomadom-bridgeinstall.sh: No such file or directory
(exit 127)

The pkg install runs the package's install.sh through bash and the Windows path arrives with its backslashes eaten. So on a Windows box the verb reports ok:false, failed:6 and installs nothing; ~/.claude/skills gains no bridge skill. (The ab installer's own bundled-skills hook is unaffected — that is how a local Claude Desktop still gets ab's core skills.)

On gallia (the Linux container, adom-wiki 1.12.2): every entry fails with unrecognized subcommand 'pkg' — that box's adom-wiki predates the pkg verbs. An environment problem, not ab's, but it means the container path is also unproven right now.

Asks: (1) make sync_skills work on Windows (quote/convert the path, or ask adom-wiki to install without bash), (2) have it report a clear, actionable failure rather than failed: N with the raw bash error, (3) decide whether Windows should use the pkg's own install at all, since a local agent there already gets skills from the installer. Meanwhile the discovery path that does work everywhere is commands / commands {"bridge":"<name>"} / bridge_info {"name"} (docs + skillPkg) — all proven on arav-rog, ConfRoomROG and winvm today.

1 Reply

John Lauer · 1mo ago

Fixed in 2.1.151 (insiders; pkg 2.1.151).

A skill package's install.sh is a Linux-container step. On Windows it ran through bash with a path whose separators bash ate and exited 127, so sync_skills reported failures and linked nothing — while adom-wiki delivers the skills itself and only the package's own script was failing. ab now skips the package's scripts on Windows, and retries without them anywhere a script failure is what broke the install; the reply carries scriptsSkipped (which packages ran without their script) and gives every remaining failure a _next with the exact command to run by hand.

Proof, both Windows boxes on 2.1.151 (CLI 2.1.151), with pup-bridge and kicad-bridge deleted from ~/.claude/skills first so the install had to do real work:

arav-rog: ok=True bridgesSeen=6 synced=6 failed=0 scriptsSkipped=6
winvm:    ok=True bridgesSeen=5 synced=5 failed=0 scriptsSkipped=5
skills present after: kicad-bridge, pup-bridge, fusion-bridge + 30 fusion-* skills
(before: ok=False, 6 of 6 failed with /bin/bash: C:Usersaravproject…install.sh: No such file or directory)

The container half of the same verb is still unproven: gallia's adom-wiki is 1.12.2, which predates the pkg subcommand, so every entry there fails with unrecognized subcommand 'pkg'. That is the box's CLI, not ab — worth updating gallia's adom-wiki when convenient.

John Lauer closed this · 1mo ago