Skill: Adom Bridge now runs on Grok Bot's computer (keep it running, one copy, files, recovery, updates)

Overview Files Skills Discover Packages Releases Dependencies Issues1 Breadcrumbs Pull Requests Activity

Closed general

John Lauer · 5d ago ·closed by John Lauer

Skill suggestion: Adom Bridge now runs on Grok Bot's computer. Please teach the agent how to look after it.

Since 2026-10-15 the agent box (grok-bot-vm-155244935) runs Adom Bridge 2.1.176 for Linux (AppImage). It's signed in as John and trusted in his Adom Mesh, so Hydrogen and his other machines drive it with adom-bridge --target grok-bot-vm-155244935 .... kicad-bridge is porting to it (adom/kicad-bridge#127).

What the agent on the box should know (a short section in grok-anywhere, or a new grok-box-adom-bridge skill):

Is it running? ~/.local/bin/adom-bridge-app-ensure starts it if not; it's quiet and idempotent. It's already called from ~/.profile and ~/.bashrc, because nothing on this box restarts processes after a reboot. After a reboot, run it once at the start of a session.
Never start a second copy by hand. There's no single-instance lock on this box (no D-Bus session bus). Two copies share one identity and kick each other off the relay every ~40 s. Use the ensure script, never run.sh directly, never the AppImage directly.
Talk to it locally: adom-bridge --ai-thread "Grok Bot" <verb> with no --target reaches the local app (port from ~/.adom/direct-api-port). Use --target <name> for John's other machines.
Files:
- app: ~/.local/share/adom-bridge-app/ (adom-bridge-app.AppImage symlink, run.sh, app.log)
- libEGL: libs/, unpacked there because the system package lock was stuck. It survives a recovery.
- config: ~/.adom/
After an "Update Bot's Computer" recovery: nothing should need reinstalling, since everything lives under home. If the app won't start with a missing libEGL.so.1, the libs/ folder is gone: reinstall libegl1 + libegl-mesa0 with apt, or unpack the .debs into libs/ again.
The old relay is gone. adom-bridge serve (port 8765, default token) was stopped on purpose (adom/adom-bridge#241). Don't restart it; the app connects out to John's relays and the mesh itself.
Updates: there's no Linux self-update yet. The Adom Bridge thread on AdomLapper updates it remotely. If asked to update by hand: adom-wiki release download john/adom-bridge-linux <ver> --platform linux, check the sha256, repoint the adom-bridge-app.AppImage symlink, stop all copies, run the ensure script.

1 Reply

John Lauer · 5d ago

Done in 1.3.11: a new section, "Adom Bridge on this computer (the agent box)", in grok-anywhere. It covers all seven points: the ensure script, one copy only, local calls, files, recovery, the retired serve relay, and updates. grok-webhook now points callers at --target grok-bot-vm-155244935 as the fast channel, with the webhook as the fallback when the box is not in targets.

Checked on the box before writing (read-only):

Bridge 2.1.176 answers.
~/.profile and ~/.bashrc call the ensure script.
Exactly one app process is running.
No adom-bridge serve is running.
libs/ and the .debs in debs/ are present.

Correction to the suggested wording: pgrep adom-bridge-app matches only the AppImage launcher, and the real app is the extracted appimage_extracted…/usr/bin/adom-bridge, which is what the ensure script checks. So the skill counts and stops copies with appimage_extracted.*/usr/bin/adom-bridge (stop also kills the launcher).

Installed on the box: adom-wiki pkg update grok-bridge took it from 1.2.2 to 1.3.11 in both ~/.grok/skills and ~/.claude/skills, so the agent there reads the new section.