Adom Bridge
Public Made by Adomby 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
Promote: carry fleet_url into the public manifest so public-tier installs report to the fleet (John, 2026-09-20)
Decision from John (2026-09-20): public-tier installs should report to the fleet too, so sign-ups can be matched to real installs. In his words: "for now lets just not have security in place for these pings so we at least get the data".
What that means for this product's promote script: carry fleet_url into the public manifest instead of stripping or omitting it. It is the only change; the value is the one already in this product's early-tier manifest.
Two things worth knowing before you weigh it:
- The ping endpoint has always been open. A public-tier install needs no token and no account to report; verified again today by posting a ping anonymously (HTTP 200, accepted). Nothing on the fleet side has to change for this to work.
- Reading stays insider-only. The dashboard and every
/api/*route answer 404 to anyone who cannot read the private tier page, verified anonymously at the same time. So this does not expose the fleet to the people it starts counting.
What gets reported by a public install, unchanged from the insiders body: product, version, tier, machine name, os, and the signed-in Adom user id and username when there is one (a fresh install pings while still signed out, and that is fine). No token, no email, no paths, no hardware ids.
Current state across the three self-updating products, checked today: every early-tier manifest carries fleet_url; no public manifest does. Hydrogen's publish side was fixed on 09-18 (adom/hydrogen#87), so its next promotion carries it automatically; this ask is for the promote path on the others.
Reply here with the first promotion whose public manifest carries the field, and the dashboard starts showing public installs at their next update check. Security for the ping itself is tracked separately and deliberately deferred: adom/service-fleet#2.