Grok Bot

@@ -1,6 +1,6 @@ {   "slug": "grok-bridge",-  "version": "1.3.11",+  "version": "1.3.12",   "type": "app",   "description": "Grok Bridge lets Adom talk to Grok Bot. Adom's AI environment is for electrical engineers: any provider (Claude, Codex, Grok, Gemini, \u2026), any desktop power tool, through Adom Bridge. grok_* open/close/resize/screenshot/record the app, read the thread, and create bots/channels via webhook.",   "keywords": [@@ -144,5 +144,5 @@   "hero": {     "path": "docs/hero.png"   },-  "changelog": "Skill: Adom Bridge now runs on Grok Bot's computer; grok-anywhere teaches the agent there to keep one copy running, where its files live, recovery and updates; grok-webhook points callers at --target grok-bot-vm-155244935."+  "changelog": "Skill: Adom Bridge on Grok Bot's computer updates itself (apply_update), carries its own EGL so libs/ is gone, and the old serve relay stays stopped with how to find what restarts it." }

@@ -4,7 +4,7 @@   "type": "app",   "title": "Grok Bot",   "brief": "Grok Bridge lets Adom talk to Grok Bot. Adom's AI environment is for electrical engineers: any provider, any desktop power tool, one place.",-  "version": "1.3.11",+  "version": "1.3.12",   "hero": {     "type": "image",     "path": "screenshots/hero.png"@@ -163,5 +163,5 @@   "dependencies": {     "adom/adom-bridge": "^2.0.0"   },-  "changelog": "Skill: Adom Bridge now runs on Grok Bot's computer; grok-anywhere teaches the agent there to keep one copy running, where its files live, recovery and updates; grok-webhook points callers at --target grok-bot-vm-155244935."+  "changelog": "Skill: Adom Bridge on Grok Bot's computer updates itself (apply_update), carries its own EGL so libs/ is gone, and the old serve relay stays stopped with how to find what restarts it." }\ No newline at end of file

@@ -58,20 +58,17 @@ Since 2026-10-15 this box (hostname `grok-bot-vm-155244935`) runs **Adom Bridge 2. **Never start a second copy by hand.** This box has no single-instance lock (no D-Bus session bus). Two copies share one identity and knock each other off the relay about every 40 s. Always use the ensure script: never `run.sh` and never the AppImage directly. To check, `pgrep -fa 'appimage_extracted.*/usr/bin/adom-bridge'` should list exactly one process. That is the real app, and the same test the ensure script uses; `adom-bridge-app` alone matches only the AppImage launcher. 3. **Talk to it locally:** `adom-bridge --ai-thread "Grok Bot" <verb>` with no `--target` reaches this box's app (its port is in `~/.adom/direct-api-port`). `--target <name>` reaches the user's other machines. 4. **Files:**-   - app: `~/.local/share/adom-bridge-app/` holds the `adom-bridge-app.AppImage` symlink to the current version, `run.sh` and `app.log`.-   - `libs/` in that folder holds libEGL, unpacked there because the system package lock was stuck. It survives a recovery.+   - app: `~/.local/share/adom-bridge-app/` holds the `adom-bridge-app.AppImage` symlink to the current version, the previous version (kept for rollback), `run.sh` and `app.log`.    - config: `~/.adom/`.-5. **After an "Update Bot's Computer" recovery** nothing should need reinstalling, because everything lives under home. If the app will not start and `app.log` mentions a missing `libEGL.so.1`, the `libs/` folder is gone. Reinstall `libegl1` and `libegl-mesa0` with apt, or unpack the `.deb`s kept in `debs/` (libegl1, libegl-mesa0, libgbm1, libgles2, libglvnd0) into `libs/` again.-6. **The old relay is gone on purpose.** `adom-bridge serve` (port 8765) was stopped for good (adom/adom-bridge#241). Do not restart it: the app connects out to the user's relays and the mesh by itself.-7. **Updates:** there is no Linux self-update yet; the Adom Bridge thread on the user's laptop updates it remotely. Update by hand only when asked:-   - `adom-wiki release download john/adom-bridge-linux <ver> --platform linux`-   - check the sha256-   - repoint the `adom-bridge-app.AppImage` symlink at the new file-   - stop every copy, the app and its launcher: `pkill -f 'appimage_extracted.*/usr/bin/adom-bridge'; pkill -f adom-bridge-app.AppImage`-   - run `~/.local/bin/adom-bridge-app-ensure`-   - confirm `pgrep -fa 'appimage_extracted.*/usr/bin/adom-bridge'` lists one process+   - The AppImage carries its own EGL (2.1.177+) and turns it on only when the machine has none, which is the case here. The old `libs/` and `debs/` folders are no longer used and can be deleted.+5. **After an "Update Bot's Computer" recovery** nothing needs reinstalling: everything lives under home, and the AppImage brings its own EGL. Run the ensure script once.+6. **The old relay stays stopped.** `adom-bridge serve` (127.0.0.1:8765/8766) was retired on purpose (adom/adom-bridge#241); the app connects out to the user's relays and the mesh by itself and never uses it. It came back once (2026-10-15, idle). If `pgrep -fa 'adom-bridge serve'` lists it:+   - find what starts it: `grep -rln 'adom-bridge serve' ~/.profile ~/.bashrc ~/.bash_profile ~/.config ~/.local/bin /etc/profile.d; crontab -l | grep adom`+   - remove that start line (it changes this computer, so the approval rule below applies), then stop it with `pkill -f 'adom-bridge serve'`+   - tell the user what started it.+7. **Updates install themselves** (2.1.177+). The app follows the insiders channel: it downloads the new AppImage, checks its sha256, repoints `adom-bridge-app.AppImage`, keeps the previous version for rollback, and starts exactly one new copy after the old one exits. This box is in `prompt` mode, so a downloaded update installs when asked: `adom-bridge apply_update` here, or `adom-bridge --target grok-bot-vm-155244935 apply_update` from another machine. Do not update it by hand. While an update applies, the box drops off `adom-bridge targets` for a few seconds. -Installing, updating or restarting it changes this computer, so the approval rule below applies.+Installing, updating (`apply_update`) or restarting it changes this computer, so the approval rule below applies.  ## Webhook requests and the user's approval