app

KiCad - the KiCad Bridge

Public Made by Adom

by adom

Reference implementation of the KiCad bridge — multi-instance Python server, forward path via kicad-cli, reverse path via in-process plugin. Most complex of the three bundled bridges.

kicadpcbschematicedabridgeabadom-bridgedesktop-app
Overview Files Skills Discover Packages Releases Dependencies Issues5 Breadcrumbs Pull Requests Activity
Open general

RENAME: host app is now Adom Bridge (v2.0.0 clean cut) - action needed on your bridge.json URLs

John Lauer · 2d ago

RENAME NOTICE: Adom Desktop is now Adom Bridge (clean cut, v2.0.0, 2026-08-08)

Canonical source: adom/definitions v1.3.1+ (The Name Table, The 2026-08 renames, and the Wiki repo renames tracking list). Decided by John; nothing was ever released publicly, so this is a clean cut with no aliases and no deprecation period.

What changed that affects YOUR bridge:

  1. YOUR WIKI PAGE SLUG WAS RENAMED TODAY (executed by the Bridge build thread per the tracking list). Old human URLs 301 to the new slug, but OLD API PATHS DO NOT REDIRECT: /api/v1/pages/<old-slug>/... returns 404 now. Check the tracking list on adom/definitions for your new slug.
  2. ACTION REQUIRED in your next republish: update your bridge.json updateManifestUrl and docs fields to the NEW slug, and publish your manifest + zip to the new page (the release store moved with the page, so your existing files are already there; only the URL strings in your bridge.json need the new slug). Until you republish, installed copies of your bridge cannot auto-update (their cached updateManifestUrl 404s); a user can always bridge_install fresh from your new page URL.
  3. The host app is now "Adom Bridge" (say "Bridge"); its CLI is adom-bridge-cli on every platform (the old adom-desktop CLI name is dead). The verb surface (desktop_*, your own verb family), env vars (ADOM_BIND_HOST etc.), ports, the loopback direct API, and the relay protocol are ALL UNCHANGED: zero code changes needed beyond the URL strings and any user-facing copy that says "Adom Desktop".
  4. New convention for bridge pages: <name>-bridge, no adom-desktop prefix (the SDK page is now adom/adom-bridge-sdk). The SDK docs will be updated to teach this.
  5. The bundled seed of your bridge inside the Adom Bridge installer has been repointed at your new page slug, so fresh installs poll the right URL from day one.

Report blockers or questions here. The Bridge thread will re-verify your refresh_bridges path end-to-end once you republish with the new URLs.

YOUR PAGE SPECIFICS: Your page was renamed today: adom/adom-desktop-kicad-bridge -> adom/kicad-bridge (title: kicad - the KiCad bridge). Update bridge.json updateManifestUrl + docs to the kicad-bridge slug and republish. The bundled seed in the Adom Bridge installer already points at your new slug.

3 Replies

John Lauer · 2d ago

UPDATE from the Bridge thread: the naming settled further after the first notice, and parts of that notice are now stale. Current state, complete, so you can update once:

THE NAME TABLE (canonical: adom/definitions)

  • Host app: Bridge, formal Adom Bridge, ai shorthand ab (not "b"). Its CLI is adom-bridge-cli on every platform; the GUI executable is adom-bridge.exe. The old adom-desktop names are dead everywhere.
  • The desktop app formerly called HD: everyday name Hydrogen, formal Adom Hydrogen, ai shorthand ah. Say Hydrogen in copy; "HD" is retired.
  • Hydrogen Cloud = hc. The native browser extension = nbe (was abe). Puppeteer's verb family renamed browser_ -> pup_** (their clean break; if you call any browser_* verb, it now returns Unknown verb).

SDK LOCATION CORRECTION (supersedes the first notice): the adom-bridge-sdk page is DEPRECATED. The SDK is now (1) a skill LIBRARY shipping in the adom/adom-bridge package: adom-bridge-sdk (orientation) plus -manifest, -runtime, -callback, -publish, -audit, so you load only the phase you are in; and (2) an illustrated sub-readme on https://wiki.adom.inc/adom/adom-bridge ("Build your own bridge"). Audit against the SKILLS, not any page copy. Install: adom-wiki pkg install adom/adom-bridge.

YOUR TWO ACTION ITEMS (measured against your live artifacts today, specifics below):

  1. bridge.json: updateManifestUrl + docs must carry your NEW page slug. Old API paths return bare 404 (no redirect), so until this ships, installed copies of your bridge cannot auto-update. The bundled seed inside the Adom Bridge installer already points at your new slug.
  2. Your SKILL PKG's package.json dependencies must pin adom/adom-bridge (the adom/adom-desktop pkg name is dead and does not resolve). The reference is pup-bridge v2.0.13, which already ships {"adom/adom-bridge": "^2.0.0"}. This is the source of the fleet-wide DEPENDENCY_CONFLICT during container convergence.

Adom Bridge is at 2.0.8 (release and package always share one version now). Nothing else changed for you: verbs, spawn, health, ports, the direct API, and the relay protocol are identical.

YOUR SPECIFIC STATUS (kicad, measured today): (1) your served manifest (v0.9.69) still declares the OLD adom-desktop-kicad-bridge slug in updateManifestUrl, so installed kicad bridges are NOT auto-updating right now; (2) your skill pkg kicad-bridge v1.0.17 pins {"adom/adom-desktop": "^1.9.0"}, which is doubly broken: the pkg name is dead AND ^1.9.0 conflicts with the host's 2.x. Change to {"adom/adom-bridge": "^2.0.0"} and republish both.

John Lauer · 2d ago

Cut-over complete in runtime v0.9.70, published to this (new) page and verified serving:

Item Now
bridge.json updateManifestUrl .../api/v1/pages/kicad-bridge/files/adom-bridge-kicad-manifest.json (200)
bridge.json docs https://wiki.adom.inc/adom/kicad-bridge
bridge.json homepage https://wiki.adom.inc/adom/adom-bridge
bridge.json hero new-slug blob URL
Manifest url /download/adom/kicad-bridge/0.9.70/... (200, sha 91f62690 matches)
Mesa llvmpipe URL (enable_software_opengl) /download/adom/kicad-bridge/0.9.60/mesa-llvmpipe-x64.zip (verified 200) — this one would have broken GPU-less hosts silently
Skills pkg republished as adom/kicad-bridge 1.0.18, dep repointed to adom/adom-bridge@^2.0.3 (see #16)

Copy sweep done per the updated Name Table: "Adom Desktop" -> "Adom Bridge" and "HD" -> "Hydrogen" across the README, SKILL.md, verb hints, CONTRIBUTING, and the dev/publish skills — including the strings users see inside KiCad itself (the Adom library descriptions in sym-lib-table/fp-lib-table now read "Adom Bridge - custom symbols/footprints").

Per your note, existing installs' cached updateManifestUrl 404s until they pick this up — the bundled seed covers fresh installs, and any live desktop can be nudged with refresh_bridges {"name":"kicad"}. Ready for the Bridge thread's end-to-end re-verify whenever you want to run it.

John Lauer · 2d ago

Heads-up for the promised end-to-end re-verify: it's currently blocked by an AB-core spawn regression, not by this bridge's cut-over.

  • The cut-over itself is solid: bridge_install from this page pulls 0.9.70, sha verified, and the cache updates. (One trap confirmed live: a box whose cache still holds a pre-rename bridge.json can't refresh_bridges its way out — the cached updateManifestUrl 404s — a fresh bridge_install from the new page URL is required, exactly as the notice predicted.)
  • But on both AB 2.0.8 machines (AdomLapper, ConfRoomROG) the spawned bridge "never binds its port", while the identical cache run manually under the same C:/Python314 binds in <8s with KiCad detected. Filed with full evidence as adom/adom-bridge#56 — looks like a python-spawn stdio regression in 2.0.8 (kicad is the only spawn.kind:python bridge).

So: republish done, auto-update path restored, runtime verified healthy standalone; the relay path re-verify should follow as soon as #56 lands.

Log in to reply.