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+3−3@@ -55,7 +55,7 @@ what listens on your network. | Mode | What it does | Does Windows ask about the firewall? | |---|---|---| | `off` | No mesh. Machines reach each other only through the cloud relay. | No | -| `relay` | **Default.** Full mesh, but every connection is carried over the Adom relay. Nothing listens on a network interface. | **No** | +| `relay` | **Recommended.** Full mesh, but every connection is carried over the Adom relay. Nothing listens on a network interface. | **No** | | `direct` | Machines connect straight to each other on the local network, with the relay as fallback. | Once, the first time | ### Why `relay` is the default, and why it is still a mesh @@ -318,7 +318,7 @@ Worth knowing, because it looks like a bug: | Setting | Values | Default | |---|---|---| -| `mesh_mode` | `off`, `relay`, `direct` | `relay` | +| `mesh_mode` | `off`, `relay`, `direct` | `off` on a new install (2.1.174); an upgrade keeps its mode | | `cross_box_prompts` | on, off | on | | `cross_box_toasts` | `prompts`, `decisions`, `all` | `all` | | `cross_box_windows_toasts` | on, off | on | @@ -338,7 +338,7 @@ card everywhere. | `desktop_mesh_peers` | every same-account box: reach, link (transport, encryption, RTT, bytes), version, trust | | `desktop_mesh_trust` | `list`, `raise` (2.1.74), `revoke`, `deny`; never approve | | `desktop_ui_panel {"panel": "mesh"}` | open the Mesh view | -| `settings_set {"mesh_mode": "off" \| "relay" \| "direct"}` | the mode; `mesh_enabled: true` means `direct` | +| `settings_set {"mesh_mode": "off" \| "relay" \| "direct"}` | the mode; `mesh_enabled: true` keeps an on mesh in its mode, else turns it on as `relay` (2.1.174) | | `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.75), and `/permission/state` lists those ids as pending so Hydrogen keeps the card up |