← Commit history

Bridges section: HD + native-browser + build-your-own (fresh image paths)

John Lauer ·76580b0517 ·4mo ago ·parent a960b62
3 files changed +2−2
README.md+2−2
@@ -67,13 +67,13 @@ The point of Adom Desktop is to make the cloud AI a power user of the apps that  **Hydrogen Desktop** — build, ship, screenshot and supervise the HD dev workspace (VS Code · Claude Code · a real browser · the dev container), and embed Adom Desktop inside it — the `hd_*` lifecycle bridge: -![Hydrogen Desktop driven by Adom Desktop](screenshots/ad-hd.png)+![Hydrogen Desktop driven by Adom Desktop](screenshots/ad-hydrogen.png)  ### Build your own bridge  A bridge is just a tiny HTTP server (`/command` + `/status`) plus a `bridge.json`. Two ~80-line reference bridges ship in the repo — **hello-python** (stdlib only) and **hello-rust** (one static binary) — fork either to bridge any app on the user's machine (Altium, MATLAB, instrument SDKs, your in-house tools) to the cloud AI: -![Write your own Adom Desktop bridge](screenshots/ad-bridges-sdk.png)+![Write your own Adom Desktop bridge](screenshots/ad-bridge-sdk.png)  `adom-desktop bridge_install '{"manifestUrl":"…/bridge.json"}'` registers the verb prefix; AD auto-spawns the bridge on the first matching call and shows it in the bridge bar. 
screenshots/ad-bridge-sdk.pngadded
⋯ 1 unchanged line ⋯
screenshots/ad-hydrogen.pngadded
⋯ 1 unchanged line ⋯