Adom Bridge

@@ -4,7 +4,7 @@  **Bridges** make Adom Bridge a small operating system for AI: a bridge teaches it a new verb namespace for any app, and Adom Bridge provisions its own managed Node and Python runtimes, owns the bridge lifecycle, and keeps every bridge in a controlled loopback-only environment. And because unleashing an AI onto a whole machine only works if the human stays in charge, the **permission system** is the other half of the product: side-effecting commands from a remote AI are gated behind a human approval the AI can request but never grant itself, every command is attributed to the AI thread that issued it, and Adom Bridge binds to localhost only. Full power and full safety together are the point. -<img src="docs/main-view-v3.png" alt="Adom Bridge main window (v2.0.13)" width="900">+![Adom Bridge main window](docs/main-view.png)  - **Full desktop control:** windows, input, screenshots, UI Automation, the shell, files, the registry, WSL. - **Bridges:** first-class mini-apps. Puppeteer (browser), KiCad, Fusion 360, your real signed-in browser, Blender, or your own.@@ -14,7 +14,7 @@  ## How it works -![Architecture](docs/arch-flow-v2.svg)+![Architecture](docs/arch-flow.svg)  The cloud AI never touches your machine directly. It sends a verb to the **relay**; Adom Bridge, connected out to that relay from your desktop, executes it against Windows or forwards it to a bridge, and streams the result back. A co-resident sibling app (Hydrogen) can skip the relay and POST straight to the **loopback HTTP API** at `127.0.0.1`. @@ -105,7 +105,7 @@ Anything Adom Bridge can see, it can screenshot, losslessly, with **no focus ste  ## Recording -<img src="docs/recorder-v2.png" alt="Adom Bridge Recorder" width="420">+![Adom Bridge Recorder](docs/recorder.png)  Adom Bridge records the desktop or a browser session to video. The recorder HUD (above) **requires a `reason`** shown to the user up front, so a recording never starts silently, with live Screen/Microphone toggles and a Start/Stop control. `desktop_recorder_open {reason}` and `desktop_recorder_close` for the desktop; `pup_record_start` and `pup_record_stop` for the pup browser. Built for smooth, high-frame-rate video, not a choppy screenshot loop. @@ -189,7 +189,7 @@ These verbs inspect any icon you pass and return an `iconCheck` that explains, i  ## Settings -<img src="docs/settings-v2.png" alt="Settings" width="780">+![Settings](docs/settings.png)  Auto-connect behavior, the update channel (**prompt** / auto / off) and *restart when idle to finish updates*, the shell-approval preference, Hydrogen integration (including *exit when Hydrogen exits*), and runtime prewarming. While embedded in Hydrogen, Hydrogen-owned preferences show as *managed by Hydrogen*. @@ -209,7 +209,7 @@ Adom Bridge speaks to you through native Windows toasts via `notify_user`, under  **Basic alert.** Awareness: a build finished, a file is ready. Auto-dismisses in about 7 seconds. Add `"durationLong":true` to hold it around 25 seconds; `"level":"error"` and up do that automatically, and `"emergency"` also flashes the taskbar. -![Basic alert toast](docs/toast-basic-v2.png)+![Basic alert toast](docs/toast-basic.png)  ```bash adom-bridge-cli notify_user '{"title":"Export done","body":"gerbers.zip is ready in C:/exports."}'@@ -225,7 +225,7 @@ The response says whether the target resolved, so the AI finds out at send time  **Sticky choice with buttons that round-trip.** Stays on screen until the user clicks (no auto-dismiss). Give it an `id` you choose, then read the click back. -![Sticky toast with buttons](docs/toast-buttons-v2.png)+![Sticky toast with buttons](docs/toast-buttons.png)  ```bash adom-bridge-cli notify_user '{"id":"deploy-42","title":"Ship v2 to production?","body":"The build is green and staged.","scenario":"reminder","buttons":[{"label":"Ship it"},{"label":"Hold"}]}'@@ -233,7 +233,7 @@ adom-bridge-cli notify_user '{"id":"deploy-42","title":"Ship v2 to production?",  **Progress bar.** For a long job (a gerber export, a render). Re-fire with the SAME `id` as the job advances toward `1.0`. `body` is optional here. -![Progress bar toast](docs/toast-progress-v2.png)+![Progress bar toast](docs/toast-progress.png)  ```bash adom-bridge-cli notify_user '{"id":"job-1","title":"Exporting gerbers","progress":{"title":"myboard.kicad_pcb","value":0.6,"status":"Plotting copper layers...","valueOverride":"6 / 10 layers"}}'@@ -241,7 +241,7 @@ adom-bridge-cli notify_user '{"id":"job-1","title":"Exporting gerbers","progress  **Reply input.** The text field renders, but Windows does not return typed text over protocol activation, so it is display-only today. For a real choice, use buttons. -![Reply input toast](docs/toast-input-v2.png)+![Reply input toast](docs/toast-input.png)  ```bash adom-bridge-cli notify_user '{"title":"Quick note","body":"Leave a note for the next run.","scenario":"reminder","inputs":[{"id":"reply","type":"text","placeholder":"Type a reply..."}],"buttons":[{"label":"Send"}]}'@@ -269,7 +269,7 @@ Deep dive: [notifications](docs/notifications.md).  ## Verbs -![Core vs bridge verbs](docs/core-vs-bridge-v2.svg)+![Core vs bridge verbs](docs/core-vs-bridge.svg)  Adom Bridge core owns the generic verbs (`desktop_*`, `shell`, `ui_*`, files, `notify_user`, multi-machine). Each bridge owns its own prefix and ships its own verbs; the app relays them verbatim and stays generic. Invoke the same way on every transport, for identical JSON back: