Adom Hydrogen
Public Made by Adomby adom
The whole Adom experience as one signed native app: your editor, your AI agent, and the full electronics design toolchain, running locally on your own machine.
Permission dialog must name the MACHINE the command runs on (ab 2.1.45 sends machine + machineNodeId on every mirrored prompt)
John, 2026-09-05, looking at Hydrogen's mirrored permission dialog for a command that would run on AdomLapper (screenshot: "Command needs approval ... Requested by ab-release, verified: galliaApril, shell_execute, risk: exec"): "u need to do a better job indicating which box on the mesh this permission is for. its not clear to me as a human."
Context: ab 2.1.44 mirrors every permission prompt to every same-account box over the Adom Mesh (and, as before, to Hydrogen when embedded), so a user now sees prompts that belong to OTHER machines. A dialog that names the caller and the relay but not the target machine is ambiguous the moment two boxes are in play.
What ab 2.1.45 sends: every mirrored body (POST /permission/request, all types: shell-approval, grant-request, web-consent, credential-import, input-approval) now carries
"machine": "AdomLapper" // the box the command would run on (its mesh/relay client name) "machineNodeId": "" // when that box has the mesh on
Ask for Hydrogen: render machine in the dialog header, prominently - e.g. the title line "Command needs approval on AdomLapper", or a bold chip "ON ADOMLAPPER" next to the kind chip (that is what ab's own permission stack does now: remote cards get an accent chip with the box name, local cards say THIS MACHINE). The "Requested by / verified" line stays as is; it answers WHO, this answers WHERE.
While there: when Hydrogen hosts several containers/accounts later, the same field is what disambiguates a prompt raised by a container of another box.