bridge_list adopts any bridges-cache subfolder that holds a bridge.json as a bridge (kicad-routing-backup-* shadowed the real kicad cache on AdomLapper, 2.1.68)

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

Closed bug report

John Lauer · 2mo ago ·closed by John Lauer

Seen on AdomLapper with ab 2.1.68 (kicad-bridge#86): three timestamped backup folders next to bridges-cache/kicad (kicad-routing-backup-, each a full copy of a cache, so each has a bridge.json) made bridge_list report name:kicad at .../bridges-cache/kicad-routing-backup-20260905T181827604746 with version 0.10.0-dev.per-net.1 while the canonical bridges-cache/kicad held 0.9.342. Discovery seems to walk every subfolder and key by the name inside bridge.json, so a backup copy shadows the real cache and an install or status read can target the wrong folder. Ask: key discovery by the folder name (bridges-cache/), ignore subfolders whose name does not match the bridge.json name, and mention them as 'ignored: ' in bridge_list so a stray copy is visible instead of adopted. Workaround applied: the backup folders were moved out of bridges-cache into a sibling bridge-backups folder on AdomLapper, arav-rog and winvm; the kicad bridge tooling now writes its backups there.

1 Reply

John Lauer · 2mo ago

Fixed in ab 2.1.71 (insiders manifest live, fleet updating). The bridges-cache scan is now keyed by FOLDER name for the cache source: a folder whose bridge.json names a different bridge is not adopted, and bridge_list lists it as state ignored with the reason and path (ignored: folder "kicad-routing-backup-..." holds a bridge.json named "kicad"; a cache bridge lives at bridges-cache/). Bundled dirs keep the manifest-name rule because pup's dir and name differ by design. Proved on AdomLapper 2.1.71: a temporary copy bridges-cache/kicad-zz-backup-test showed as ignored while the kicad row stayed on bridges-cache/kicad at 0.9.347; the copy was removed afterwards. One thing you will see: an install's own temporary .pending- extraction folder is listed as ignored for the seconds it exists, and a stale one from an aborted install stays listed, which is deliberate so it is visible. Your workaround (backups in a sibling bridge-backups folder) is also the documented rule now.

John Lauer closed this · 2mo ago