Adom Bridge

@@ -1,6 +1,6 @@ # Adom Bridge -**Unleash your AI onto your full PC: full power, full safety.** Every AI you use today is locked in a box: a cloud agent lives in a container with no hands, and a chat app can talk about your files but cannot touch them. Adom Bridge inverts that. It lets the AI break out of the box it runs in and onto your real machine, so the AI manages and runs your entire laptop as you, without you doing anything manually: launch apps, move files, drive any window, control KiCad, Fusion 360, Altium, Blender, or your real signed-in browser. It does not matter where your AI lives. A cloud agent reaches your desktop over the relay; a local one (Claude Desktop, Claude Code, Codex, anything) drives the same machine over loopback. It ships with **Hydrogen Desktop** and installs standalone too, and standalone users get the full value.+**Unleash your AI onto your full PC: full power, full safety.** Every AI you use today is locked in a box: a cloud agent lives in a container with no hands, and a chat app can talk about your files but cannot touch them. Adom Bridge inverts that. It lets the AI break out of the box it runs in and onto your real machine, so the AI manages and runs your entire laptop as you, without you doing anything manually: launch apps, move files, drive any window, control KiCad, Fusion 360, Altium, Blender, or your real signed-in browser. It does not matter where your AI lives. A cloud agent reaches your desktop over the relay; a local one (Claude Desktop, Claude Code, Codex, anything) drives the same machine over loopback. It ships with **Hydrogen** and installs standalone too, and standalone users get the full value.  **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. @@ -16,7 +16,7 @@  ![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 Desktop) can skip the relay and POST straight to the **loopback HTTP API** at `127.0.0.1`.+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`.  ``` Adom container (this package)            User's laptop@@ -38,11 +38,10 @@ That installs the **container-side** pieces: the `adom-bridge` CLI (SHA256-verif | Skill | What Claude learns | |---|---| | `adom-bridge` | the main verb catalog: screenshots, files, shell, windows, notifications |-| `adom-bridge-pup` | real-Chrome (Puppeteer) automation: sessions, tabs, eval, recording | | `adom-bridge-notify` | native Windows toasts: progress bars, sticky reminders, buttons that round-trip |-| `adom-bridge-bridge-sdk` | author your own bridge: `bridge.json`, health/describe/rich-hint contracts, lifecycle |-| `adom-bridge-bridge-ownership` | the boundary: what AD core owns versus what a bridge author owns |-| `adom-bridge-multi-ad` | address multiple Adom Bridges on one relay (`--target`, fan-out) |+| `adom-bridge-sdk` (+ `-manifest`, `-runtime`, `-callback`, `-publish`, `-audit`) | author your own bridge: a skill library split by phase, so only the part you need loads |+| `adom-bridge-ownership` | the boundary: what AD core owns versus what a bridge author owns |+| `adom-bridge-multi-machine` | address multiple Adom Bridges on one relay (`--target`, fan-out) | | `adom-bridge-direct-api` | the loopback HTTP API for sibling apps | | `adom-bridge-installer`, `adom-bridge-windows-host`, `adom-bridge-discovery` | install, host, and discovery details | @@ -60,13 +59,13 @@ Sign in to your Adom account inside the app (Connections panel) and your cloud c  One desktop can connect to many containers, many desktops can share one container, and both at once. Address any desktop by name with `--target`. Deep dive with a topology diagram: [connection topology](docs/topology.md). -## Running under Hydrogen Desktop+## Running under Hydrogen -When Hydrogen Desktop is present it runs Adom Bridge embedded: hidden window, HD-owned permission prompts, and a distinct taskbar tile. If HD ever goes away, Adom Bridge comes back standalone so your machine stays reachable. Deep dive: [how AD interacts with Hydrogen Desktop](docs/hydrogen-desktop.md).+When Hydrogen is present it runs Adom Bridge embedded: hidden window, Hydrogen-owned permission prompts, and a distinct taskbar tile. If Hydrogen ever goes away, Adom Bridge comes back standalone so your machine stays reachable. Deep dive: [how AD interacts with Hydrogen](docs/hydrogen-desktop.md).  ## The laptop GUI -The **Windows GUI** installs separately: a signed NSIS installer served from this page (*Download for your machine* above; Hydrogen Desktop installs it automatically). It installs to `%LOCALAPPDATA%\Adom Bridge\`, adds a tray icon, starts on login, and **auto-updates itself** from this page's `version.json` (prompt by default; every 4h and on launch).+The **Windows GUI** installs separately: a signed NSIS installer served from this page (*Download for your machine* above; Hydrogen installs it automatically). It installs to `%LOCALAPPDATA%\Adom Bridge\`, adds a tray icon, starts on login, and **auto-updates itself** from this page's `version.json` (prompt by default; every 4h and on launch).  The main window (top) puts everything on one surface: **Connections** (each relay plus the other Adom Bridges on it as peers), the **Activity Log** (every command, badged by source and type, filterable), the **Bridges sidebar** (installed bridges as mini-app cards), the provisioned **Runtimes**, and the footer approval bar. @@ -79,7 +78,7 @@ Everything a real user installs comes from this page. | Artifact | Platform | What it is | How to get it | |---|---|---|---| | Signed installer (NSIS) | Windows x64 | The GUI desktop app. Azure Trusted Signing. Installs to `%LOCALAPPDATA%\Adom Bridge\` and auto-updates. | The *Download for your machine* box at the top of this page. This is the one promoted Windows download. |-| CLI + skills package | Linux (container) | The `adom-bridge` CLI and Claude skill set for a cloud container driving your desktop remotely. Not needed if you use Hydrogen Desktop, which bundles Adom Bridge. SHA256-verified on install. | `adom-wiki pkg install adom/adom-bridge` |+| CLI + skills package | Linux (container) | The `adom-bridge` CLI and Claude skill set for a cloud container driving your desktop remotely. Not needed if you use Hydrogen, which bundles Adom Bridge. SHA256-verified on install. | `adom-wiki pkg install adom/adom-bridge` | | `version.json` | manifest | The auto-update manifest the GUI polls: per-platform installer URL, SHA256, and size. | Read automatically by the app; you never fetch it by hand. |  The Windows GUI installer is the only promoted Windows download. There is intentionally no standalone Windows CLI download. macOS is planned; the manifest reserves a slot for it.@@ -96,7 +95,7 @@ Adom Bridge polls the wiki manifest on launch and every 4 hours. Every release i  You set your preference once in **Settings, Updates**: Prompt (default), Auto, or Off. A normal release carries no priority; the emergency tier is a deliberate, per-incident action. -**When a normal update actually installs.** Adom Bridge lives in the tray and can run for weeks without a restart, so a Prompt-mode update you never click would never install. The restart schedule closes that: once an update is downloaded AND you have been away from the keyboard for about 15 minutes AND AD is not mid-task, it installs and relaunches quietly. It is idle-based, not a fixed clock, so it never interrupts active work or an overnight job, and restarting Adom Bridge has no effect on your other apps (it reconnects in seconds). Turn it off in Settings, Updates, "Restart when idle to finish updates," and a Prompt-mode update simply waits for your click. Auto installs immediately; Off never auto-installs (except an Emergency release). Embedded in Hydrogen Desktop, HD owns the restart timing.+**When a normal update actually installs.** Adom Bridge lives in the tray and can run for weeks without a restart, so a Prompt-mode update you never click would never install. The restart schedule closes that: once an update is downloaded AND you have been away from the keyboard for about 15 minutes AND AD is not mid-task, it installs and relaunches quietly. It is idle-based, not a fixed clock, so it never interrupts active work or an overnight job, and restarting Adom Bridge has no effect on your other apps (it reconnects in seconds). Turn it off in Settings, Updates, "Restart when idle to finish updates," and a Prompt-mode update simply waits for your click. Auto installs immediately; Off never auto-installs (except an Emergency release). Embedded in Hydrogen, Hydrogen owns the restart timing.  Deep dive on every update lane (app, bridges, container package, skills) and the network-traffic math: [how updates work](docs/updates.md). @@ -146,11 +145,11 @@ Parametric modeling scripts and exports, plus fast indexed cloud-file search thr  Headless Python scripting and renders. -### Hydrogen Desktop (`hd_*`)+### Hydrogen (`hd_*`) -![Hydrogen Desktop bridge card](docs/bridge-card-hd.png)+![Hydrogen bridge card](docs/bridge-card-hd.png) -The local dev-environment app AD can embed into; AD relays HD's runtime state and drives its lifecycle.+The local dev-environment app AD can embed into; AD relays Hydrogen's runtime state and drives its lifecycle.  Install a third-party bridge by pasting its manifest URL, or `bridge_install {"manifestUrl":"..."}`. @@ -173,9 +172,9 @@ AD's window carries a mode-specific app identity, so the taskbar button swaps it | Icon | Mode | Taskbar name | Meaning | |:---:|:---|:---|:---| | <img src="docs/taskbar-standalone.png" alt="Standalone: muted Adom tile" width="88"> | **Standalone** | Adom Bridge | AD running on its own. The default for a normal install. |-| <img src="docs/taskbar-embedded.png" alt="Embedded: vivid Adom tile" width="88"> | **Embedded** | Adom Bridge HD Embedded | Hydrogen Desktop launched AD and drives its lifecycle. |+| <img src="docs/taskbar-embedded.png" alt="Embedded: vivid Adom tile" width="88"> | **Embedded** | Adom Bridge Hydrogen Embedded | Hydrogen launched AD and drives its lifecycle. | -Muted "Adom Bridge" = AD by itself; vivid "Adom Bridge HD Embedded" = HD has the helm. Each mode is a registered Windows app identity, and flipping the window between them makes the shell rebuild the button with the other identity's icon and name. Because the modes are distinct identities, a taskbar pin made in one mode shows the running window as a separate button while AD is in the other mode.+Muted "Adom Bridge" = AD by itself; vivid "Adom Bridge Hydrogen Embedded" = Hydrogen has the helm. Each mode is a registered Windows app identity, and flipping the window between them makes the shell rebuild the button with the other identity's icon and name. Because the modes are distinct identities, a taskbar pin made in one mode shows the running window as a separate button while AD is in the other mode.  ## Window identity (branding a window the AI drives) @@ -192,7 +191,7 @@ These verbs inspect any icon you pass and return an `iconCheck` that explains, i  ![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 Desktop integration (including *exit when HD exits*), and runtime prewarming. While embedded in HD, HD-owned preferences show as *managed by Hydrogen Desktop*.+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*.  ## Security and the approval gate @@ -200,7 +199,7 @@ Auto-connect behavior, the update channel (**prompt** / auto / off) and *restart  **The trust boundary is install-consent plus the localhost bind.** Installing the app (and each bridge) is you granting permission for the AI to drive your machine; if you do not want that, uninstall. And the app plus every bridge binds `127.0.0.1` **only, never `0.0.0.0`**, so a caller must already be a program you installed on your own machine to reach it. No network attack surface by construction. -On top of that, the **remote cloud-AI path is approval-gated.** Verbs that run code or change the machine (`shell_execute`, `run_script`, `launch_process`, `write_file`, `registry_*`, `process_kill`, and so on) require a human grant when they arrive over the *relay*: **+1hr / +24hr** (time-boxed), **Bypass** (indefinite), or **Revoke**. The grant is human-only; local callers (your CLI, HD, bridges) are trusted by transport and never prompt; read-only verbs are never gated.+On top of that, the **remote cloud-AI path is approval-gated.** Verbs that run code or change the machine (`shell_execute`, `run_script`, `launch_process`, `write_file`, `registry_*`, `process_kill`, and so on) require a human grant when they arrive over the *relay*: **+1hr / +24hr** (time-boxed), **Bypass** (indefinite), or **Revoke**. The grant is human-only; local callers (your CLI, Hydrogen, bridges) are trusted by transport and never prompt; read-only verbs are never gated.  Deep dive: [permissions](docs/permissions.md) (what each Approve choice means, and how to revoke). 

@@ -1,87 +1,88 @@-{-  "slug": "adom-bridge",-  "version": "2.0.3",-  "type": "app",-  "brief": "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-only permission system keeps you in charge of every side-effecting command.",-  "description": "Install this package in a cloud or Hydrogen Desktop container, not on the PC. It delivers two things: the Linux adom-bridge-cli (linked onto PATH) and the Claude skill set that teaches an AI every desktop verb (shell, files, screenshots, windows, notifications, KiCad, Fusion 360, browser automation). The CLI drives the Adom Bridge app running on your Windows PC over the relay; the Windows app itself is the separate installer in the Download box, not part of this package. Run adom-wiki pkg update to keep the CLI and skills current.",-  "discovery_pitch": "Use when a cloud AI needs to reach a real Windows desktop: run shell commands, capture screenshots, drive native apps and browsers, transfer files, and control KiCad / Fusion 360 / third-party bridges.",-  "discovery_triggers": [-    "control my windows desktop from the cloud",-    "drive a native windows app",-    "take a screenshot of a window on my pc",-    "run a shell command on my windows machine",-    "automate kicad or fusion 360",-    "open a browser on my desktop and click around",-    "send a file to my laptop",-    "show me a notification on my computer",-    "adom bridge",-    "bridge to my pc",-    "b win",-    "adom desktop"-  ],-  "sample_prompts": [-    {-      "label": "Screenshot a window",-      "prompt": "Take a screenshot of the Fusion 360 window on my desktop"-    },-    {-      "label": "Run a command",-      "prompt": "Run git status on my Windows machine and show me the output"-    },-    {-      "label": "Drive a bridge",-      "prompt": "Open my latest KiCad project and export the Gerbers"-    },-    {-      "label": "Automate the browser",-      "prompt": "Open Chrome on my desktop and log into the dashboard"-    },-    {-      "label": "Transfer a file",-      "prompt": "Pull the build log from C:\\temp on my laptop"-    }-  ],-  "keywords": [-    "adom-bridge",-    "tauri",-    "claude-code",-    "bridge",-    "kicad",-    "fusion360",-    "puppeteer",-    "chrome",-    "websocket",-    "cli",-    "screenshot",-    "recording",-    "desktop-automation",-    "adom-desktop"-  ],-  "tags": [-    "adom-bridge",-    "tauri",-    "claude-code",-    "bridge",-    "kicad",-    "fusion360",-    "puppeteer",-    "desktop-automation"-  ],-  "scripts": {-    "install": "./install.sh",-    "uninstall": "./uninstall.sh"-  },-  "install": {-    "binary_name": "adom-bridge"-  },-  "dependencies": {},-  "files": [-    "SKILL.md",-    "README.md",-    "install.sh",-    "uninstall.sh",-    "skills/**",-    "dist/**",-    "version.json"-  ]-}+{
+  "slug": "adom-bridge",
+  "version": "2.0.4",
+  "type": "app",
+  "brief": "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-only permission system keeps you in charge of every side-effecting command.",
+  "description": "Install this package in a cloud or Hydrogen Desktop container, not on the PC. It delivers two things: the Linux adom-bridge-cli (linked onto PATH) and the Claude skill set that teaches an AI every desktop verb (shell, files, screenshots, windows, notifications, KiCad, Fusion 360, browser automation). The CLI drives the Adom Bridge app running on your Windows PC over the relay; the Windows app itself is the separate installer in the Download box, not part of this package. Run adom-wiki pkg update to keep the CLI and skills current.",
+  "discovery_pitch": "Use when a cloud AI needs to reach a real Windows desktop: run shell commands, capture screenshots, drive native apps and browsers, transfer files, and control KiCad / Fusion 360 / third-party bridges.",
+  "discovery_triggers": [
+    "control my windows desktop from the cloud",
+    "drive a native windows app",
+    "take a screenshot of a window on my pc",
+    "run a shell command on my windows machine",
+    "automate kicad or fusion 360",
+    "open a browser on my desktop and click around",
+    "send a file to my laptop",
+    "show me a notification on my computer",
+    "adom bridge",
+    "bridge to my pc",
+    "ab win",
+    "adom desktop",
+    "ab"
+  ],
+  "sample_prompts": [
+    {
+      "label": "Screenshot a window",
+      "prompt": "Take a screenshot of the Fusion 360 window on my desktop"
+    },
+    {
+      "label": "Run a command",
+      "prompt": "Run git status on my Windows machine and show me the output"
+    },
+    {
+      "label": "Drive a bridge",
+      "prompt": "Open my latest KiCad project and export the Gerbers"
+    },
+    {
+      "label": "Automate the browser",
+      "prompt": "Open Chrome on my desktop and log into the dashboard"
+    },
+    {
+      "label": "Transfer a file",
+      "prompt": "Pull the build log from C:\\temp on my laptop"
+    }
+  ],
+  "keywords": [
+    "adom-bridge",
+    "tauri",
+    "claude-code",
+    "bridge",
+    "kicad",
+    "fusion360",
+    "puppeteer",
+    "chrome",
+    "websocket",
+    "cli",
+    "screenshot",
+    "recording",
+    "desktop-automation",
+    "adom-desktop"
+  ],
+  "tags": [
+    "adom-bridge",
+    "tauri",
+    "claude-code",
+    "bridge",
+    "kicad",
+    "fusion360",
+    "puppeteer",
+    "desktop-automation"
+  ],
+  "scripts": {
+    "install": "./install.sh",
+    "uninstall": "./uninstall.sh"
+  },
+  "install": {
+    "binary_name": "adom-bridge"
+  },
+  "dependencies": {},
+  "files": [
+    "SKILL.md",
+    "README.md",
+    "install.sh",
+    "uninstall.sh",
+    "skills/**",
+    "dist/**",
+    "version.json"
+  ]
+}