Keep the agent computer awake: is there a setting, a long run, or a wake API?

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

Closed general

John Lauer · 5d ago ·closed by John Lauer

Question from John: is there a way to keep the Grok agent computer awake?

The agent computer (grok-bot-vm-155244935) is paused a few minutes after each agent run ends, and resumes when the next run starts. The measurements are in #9. John wants it to stay up: it runs Adom Bridge on his mesh, the kicad-bridge build thread drives KiCad on it over that mesh (adom/kicad-bridge#127), and it is meant to run long KiCad jobs unattended.

Please find out and report back:

Does Grok Bot have a setting (Settings > Computer, a plan option, a per-bot setting) that keeps the computer running between agent runs, or for a set time? What is it called, and can grok-bridge read or set it (grok_settings)?
If there is no setting: does the computer stay up as long as an agent run is in progress? Then a long-running agent task (for example, a run that waits on a KiCad job) would keep it awake. What is the longest run allowed, and what does it cost?
Is there an API (Cursor automation or Grok Bot) to resume the computer on demand without a chat message? A grok_wake verb on top of it would let mesh callers wake the box before they drive it.

Whatever the answer, please add it to the grok-anywhere skill: "the computer pauses when the agent is idle; here is how to keep it awake / wake it".

1 Reply

John Lauer · 5d ago

Answers (details in #9):

Setting: no. Settings > General, Computer and Usage & Billing have nothing that keeps the computer running between runs (checked on AdomLapper 2026-10-15). grok-bridge cannot read or set what is not there.
A run in progress keeps it awake: yes. That is how grok_wake works: a run that only sleeps. It costs Grok usage like any agent run; the account showed 19% of the weekly limit used, with the on-demand cap at $80. I found no documented maximum run length. Runs of 3 minutes are proven, and grok_wake caps at 30 minutes per call.
Wake API without a chat message: none in Grok Bot's UI or settings. The only triggers are a chat message or the webhook routine. grok_wake uses the webhook and falls back to the chat (grok_chat_send), so a mesh caller can call it before driving the box.

The grok-anywhere skill now says the computer pauses when the agent is idle and how to keep it awake. Shipped in 1.3.15 (insiders). For a box that must run KiCad jobs unattended for hours, the honest answer is that Grok does not offer it today: a sleep run of up to 30 minutes per wake, repeated, is the workaround, and each one costs usage.