app

Grok Bot

Public Made by Adom

by adom

Grok Bridge lets Adom talk to Grok Bot. Adom's AI environment is for electrical engineers: any provider, any desktop power tool, one place.

grokgrok-botcursoradom-bridgebridgeskillsanywhere
Overview Files Skills Discover Packages Releases Dependencies Issues1 Breadcrumbs Pull Requests Activity
Closed general

The agent computer is paused between agent runs; Adom Bridge on it is unreachable while the agent is idle

John Lauer · 5d ago ·closed by John Lauer

The agent computer is paused between agent runs, so nothing on the mesh can reach it while the agent is idle

Measured today (2026-10-15) on grok-bot-vm-155244935 with Adom Bridge running on it:

  • At 15:31:55 UTC the box dropped off gallia's relay mid-session. At 15:37:59, the moment a Grok Bot chat message started an agent run, every timer in the Adom Bridge process fired at once: its relay watchdog, its 30 s keepalive, the iroh mesh client's ping timeout, tracing spans. It then reconnected in 1 second.
  • The two clocks disagree over that gap: the watchdog (wall clock) counted 466 s with no relay message, the keepalive (monotonic clock) only 31 s. The monotonic clock stops only when the machine itself is not running.
  • At 13:52 UTC uptime was 8 h 42 min, while the app's log on the box starts at 01:16 UTC, 12.6 hours earlier: about 4 hours of the day the box was not running.
  • The earlier drops follow the same pattern: 13:16 to 13:50, 13:55 to 14:47, 15:04 to 15:26. Each ended when an agent run started (a chat message or a webhook).

So the computer is suspended a few minutes after an agent run ends. For a box meant to run long KiCad jobs and to be driven over the Adom mesh (adom/kicad-bridge#127 is blocked on exactly this), that is the whole problem.

Asks:

  1. Is there a Grok Bot setting (Settings > Computer?) that keeps the computer running between agent runs, or for a set time? If so, the skill should say how to turn it on, and grok_settings could report it.
  2. A grok_wake (or grok_computer_wake) verb that starts a minimal agent run just to resume the computer, and answers when it is running. Callers on the mesh (the kicad-bridge build thread) could call it before driving the box. Today the only way is a chat message or a webhook fire, and the webhook is rate-limited (#8).
  3. The skill should explain this: "the computer is paused when the agent is idle; anything that must run unattended needs the computer kept awake".

1 Reply

John Lauer · 5d ago

Answered with code in 1.3.15.

  1. Setting: none. I read Grok Bot's Settings > General, Computer and Usage & Billing on AdomLapper. Computer has only Execution on this computer, Route traffic, Update Bot's Computer and Reset Bot's Computer; nothing keeps the computer running. grok_settings cannot report what does not exist.
  2. grok_wake {minutes (max 30), reason} starts an agent run that only runs sleep <N min>. A working run keeps the computer up, the same thing the Adom Bridge thread did by hand with "sleep 180". It goes out over the webhook, falling back to grok_chat_send when the webhook is throttled (#8), and the reply WAKE-xxxx awake-done marks the end.
    • Live test: during a 2-minute wake, shell_execute on grok-bot-vm-155244935 answered every 15 s.
    • Not proven yet: the box was already awake from a test a minute before, so this shows wake keeps it up, not a resume from pause.
  3. Skill: grok-webhook has "Waking Grok's computer". grok-anywhere tells the agent its computer pauses when idle, to run exactly sleep when asked to stay awake, and to stay in the run for long unattended jobs.

Log in to reply.