Adom Bridge on your laptop
Grok Bot auto-connects to Adom Bridge on first use — you should never copy JSON or click through a Connections panel. If the Adom Bridge LED is not green, send this to the AI.
Run grok-dashboard ensure-desktop (it calls adom-bridge setup_desktop and reconnects Adom Bridge on the laptop using the public relay URL). Do not ask me to paste JSON. Do not steal focus. Never paste webhook keys. Never kill Cursor.
Demo video
Two directions in about 30 seconds. Adom Hydrogen → Grok Bot: wiki, Fusion, KiCad, Gmail, Arduino Uno. Grok Bot → Adom Hydrogen: webhook answers land in an Adom Hydrogen thread. Play the 30s demo from the panel above to walk the dashboard; this clip is the picture of that loop.
Sample AI prompts
The Say it strip is primary. These are the power-user verbs behind those phrases.
Install from scratch
Skills pack first, then the desktop runtime from the wiki manifest. Skills ≠ runtime.
adom-wiki pkg install adom/grok-bridge
adom-bridge bridge_install '{"manifestUrl":"https://wiki.adom.inc/api/v1/pages/grok-bridge/files/adom-bridge-grok-manifest.json"}'
Auto webhook
Scrapes the Grok Bridge webhook routine pane (URL + key + header) and writes the local bind file. Never show or paste the key.
grok_webhook_ensure {}
New bot threads
Creates a named Grok Bot agent. Inbound still lands in the grok-bridge mailbox; pass agent on fire to relay.
grok_bot_create {"name":"Adom Echo"}
Two directions: Adom Hydrogen → Grok Bot vs Grok Bot → Adom Hydrogen
Adom Hydrogen → Grok Bot sends work (open Fusion, screenshot, launch apps). Grok Bot → Adom Hydrogen talks back into an Adom Hydrogen thread. There is no SendMessage / ListAgents API this dashboard can call. The working loop is fire grok_webhook_fire, then poll grok_chat_read.
grok_webhook_fire {"event":"ping","payload":{"nonce":"GB-DEMO-1"}}
# then poll grok_chat_read for the nonce (~60–120s FIFO)
Snapshots of Grok's computer
Grok does not screenshot the agent box from Grok Bot.exe. The box is Grok Bot's computer. grok_screenshot captures the Grok Bot.exe window on the desktop — different from a screenshot of the agent computer.
Have grok-bridge screenshot its computer (the agent box).
If you meant the Grok Bot.exe window, call grok_screenshot {} instead.
Launch apps on Grok's computer
Open KiCad and viewers on the agent computer. Arduino Uno board path is already on the box.
Open KiCad on grok's computer with
$HOME/kicad-offload/Arduino_Uno/Arduino_Uno.kicad_pcb
KiCad offload
Grok Bot's computer can run KiCad so the EE does not have to use their laptop. kicad is already on PATH on the box historically; install it if the LED is not green.
If KiCad is missing on grok's computer, install it there.
Then open the Arduino Uno board in the background.
adom/core bootstrap
Bootstrap a standard Adom workstation on Grok's computer in one command (skills hub, wiki, KiCad/Fusion skills).
adom-wiki pkg install adom/core