app
Adom Bridge
Public Made by Adomby adom
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-onl
← Commit history
docs/mesh.md: deciding a cross-box card in Hydrogen is 2.1.75 (the 2.1.74 route pre-empted the remote branch); /permission/state lists mirrored ids
1 file changed
+3−3
docs/mesh.md+3−3@@ -102,8 +102,8 @@ card is forwarded to Hydrogen's permission dialog: card stopped at Adom Bridge's own window and a Windows toast, and Hydrogen never showed it: you could see "Permission request on winvm, open Adom Bridge to decide it here" and find nothing in Hydrogen. Now the same card, with the machine chip, renders in Hydrogen on every box you have it- open on, and deciding it there routes the decision back to the origin with the nonce, the same- path a click in Adom Bridge takes.+ open on, and deciding it there (2.1.75) routes the decision back to the origin with the nonce,+ the same path a click in Adom Bridge takes. - **Dismissals are forwarded as well.** When the origin decides, expires, or drops a prompt, Hydrogen's copy on every other box goes down with it. A mirrored card nobody answers is dropped from the receiving box after 330 seconds (the same cap Hydrogen applies), so a stack never@@ -150,4 +150,4 @@ Hovering a box also shows its trust record: who approved it, on which machine, w | `settings_set {"mesh_mode": "off" \| "relay" \| "direct"}` | the mode; `mesh_enabled: true` means `direct` | | `settings_set {"cross_box_toasts": "prompts" \| "decisions" \| "all"}` | how much plain toast traffic crosses boxes | | `GET /status` -> `notifications.mayBeSuppressed` | whether a toast on this box may go unseen |-| `POST /permission/resolve {id, decision}` | how Hydrogen decides a card; a `remote:<peer>:<id>` id is routed back to the origin (2.1.74) |+| `POST /permission/resolve {id, decision}` | how Hydrogen decides a card; a `remote:<peer>:<id>` id is routed back to the origin (2.1.75), and `/permission/state` lists those ids as pending so Hydrogen keeps the card up |