Adom Bridge

⋯ 1 unchanged line ⋯

@@ -1,6 +1,6 @@ {
   "slug": "adom-bridge",
-  "version": "2.1.141",
+  "version": "2.1.142",
   "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.",

@@ -1,6 +1,6 @@ {   "slug": "adom-bridge",-  "version": "2.1.141",+  "version": "2.1.142",   "type": "app",   "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.",   "keywords": [

@@ -44,6 +44,16 @@ The click is recorded **durably** (a cross-process file), so both paths work eve 
 `focus` is covered next. It raises a window on screen — it does **not** tell you anything. A toast can do BOTH at once (a sticky toast with buttons + `focus:{host:true}` reveals Hydrogen on click *and* reports the click back via `wait`/`notify_events`).
 
+## Which box sees the toast (several machines, one account)
+
+A user with several Adom Bridges gets your toast on the box you address, and a copy on the others:
+
+- **No `--target`**: the toast goes to this relay's own box (from a container, the machine that hosts it). That box then MIRRORS a plain toast to every other box of the same account, shown there as `On <box>: <title>` (the receiver's Settings > Notifications > cross-box toasts, default `all`). A BUTTONED prompt (`buttons`, `wait:true`) is mirrored to every box regardless of that setting, and the human can answer it on any of them; the answer travels back to you.
+- **`--target <box>`**: addresses one box directly. With a local ab beside you (a Hydrogen container, a laptop), the CLI hands the call to it and it reaches the box over the mesh first, then the relays (2.1.142+). Without a local ab the call goes through the relay, which only knows the boxes connected to it.
+- **`targets`** lists what is reachable from here and how (`via: relay | mesh`, `path`). `target_not_found` means this relay does not hold that box; it does NOT mean the box is offline, and it does not mean the user never saw your toast (the mirror may have shown it).
+
+So to reach the human where they sit: send a buttoned prompt with no target (it follows them), or `--target` the box `targets` names. Do not conclude "the bridge cannot toast the laptop" from a `target_not_found` on one relay; check `targets` and the mirror first.
+
 ## ⭐ Start here: make the click DO something (`focus`, v1.9.162)
 
 Most notifications are **about something else on screen** — a browser waiting on a login, a dialog, an app that needs a click. If you send a bare toast, clicking it opens the Adom Bridge window, which is almost never what the user wanted. They clicked because they wanted to get to *the thing*.