Adom Bridge

⋯ 1 unchanged line ⋯

@@ -1,6 +1,6 @@ {
   "slug": "adom-bridge",
-  "version": "2.1.171",
+  "version": "2.1.172",
   "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.171",+  "version": "2.1.172",   "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": [

@@ -53,7 +53,7 @@ adom-bridge --target ConfRoomROG desktop_list_windows   # route.via tells you me 
 ## When the mesh relay will not connect (2.1.171)
 
-`desktop_mesh_status` carries `relayNote` whenever `relayConnected` is false. The commonest cause is an account the Adom mesh relay does not admit: it only lets in accounts whose token (`bridge.mesh.relayToken` in the account's cloud settings) is on its list, and `relayAuth: "none"` means this box has none. Verbs still route through the cloud command relay; only cross-network mesh paths are missing. `mesh_enabled:false` written into config.json by hand now switches the mesh off even when `mesh_mode` says relay (wiki #229).
+`desktop_mesh_status` carries `relayNote` whenever `relayConnected` is false, and `relayEnrollment` (2.1.172) says whether this machine is signed up with the Adom mesh relay. Since 2.1.172 the relay admits individual MACHINES: ab signs itself up automatically when the box is signed in to Adom (its node key signs the request, the user's session proves the account), on mesh start, daily, and whenever the relay refuses it. A box that is not signed in cannot sign up, and `relayNote` says so. Older boxes (2.1.171 and earlier) used one account-wide token (`relayAuth`). Verbs still route through the cloud command relay; only cross-network mesh paths are missing. `mesh_enabled:false` written into config.json by hand now switches the mesh off even when `mesh_mode` says relay (wiki #229).
 
 ## Who is allowed in: per-box trust (2.1.66)