Pause Grok Bot routines when the Agent Computer is unreachable

Forum reports (Sep 2, 2026, Grok Bot 0.30.0): the shared Agent Computer stays unreachable, chat sits on “waiting for the bot and computer to come online,” and webhook or scheduled routines keep firing and burning usage. Routine controls appear to need the computer online. Cursor staff (deanrie) confirmed a common cause: the desktop client fails to resolve *.cursorvm.com while the box stays online. Generic reachability: Fix Grok Bot “Can’t reach your computer”.

Restore reachability first (DNS)

Staff’s recommended fix when ISP DNS filters Cursor VM records:

1. Set DNS on the router or device to Cloudflare (1.1.1.1 / 1.0.0.1) or Google (8.8.8.8 / 8.8.4.4).
2. Set both IPv4 and IPv6 DNS so router RA does not fall back to the ISP resolver.
3. Optionally enable DNS-over-HTTPS if the ISP rewrites plain DNS.
4. Fully quit Grok Bot, reopen, and Retry once.

After DNS clears, Routine controls usually open. Switching back to a filtering resolver can break reachability again.

Pause routines once the UI opens

Official skills and routines docs:

1. Open the Bot that owns the webhook or schedule.
2. Choose View conversation details, then Routines.
3. Pause (or disable) every routine that should stop while you recover.
4. When you re-enable event webhooks, keep match rules narrow — broad listeners burn usage.

A Bot can own up to 50 routines. Deleting a routine has no undo. Hiding a Bot from the sidebar does not pause its routines. Closing the laptop does not stop background routines (Bot FAQ).

If the UI still will not open

1. Retry Recover / Update only after DNS and a full quit — official troubleshooting least-destructive order.
2. Skip a second Reset while a partial-state wipe may still be stuck; see Fix Grok Bot after a failed Reset leaves a partial state.
3. Email hi@cursor.com about usage billed while the computer was unreachable. Staff call that check account-specific; the public forum cannot adjust billing.

Collect Grok Bot version, OS, exact can’t-reach text, time zone, and whether DNS restored the box. Skip secrets.

Pitfalls

• Messaging “pause all routines” while stuck on waiting-for-computer does not reach the Bot until the computer answers.
• Successful IDE use does not prove *.cursorvm.com resolves for Grok Bot.
• Routine miss / late-queue / bot-to-bot burn how-tos cover different failure modes; pause here when burn continues under an unreachable computer.