Do you need a server to run Grok Bot 24/7? The Bot's computer vs your computer (unofficial guide)

Two different computers people mix up

The Bot's computer: a persistent cloud computer assigned to your user account. Per the docs, every Bot on your account shares it, along with browser sessions, files, and command-line credentials. Each Bot gets its own screen on it.

Your computer: the Mac or Windows machine in front of you. The docs say the cloud computer is separate from it. A Bot only runs commands on your local computer when that capability is enabled and you approve it under your local-computer policy (per-command approval with Ask every time by default, or Always allow or Never allow).

Most "do I need a server?" worries come from treating these as one machine. If the work happens on the Bot's computer, your laptop lid doesn't matter.

What the official docs say about keeping work running

The computer-and-apps page says work continues while your laptop is closed, and that you can leave the computer preview while work continues. It also says that closing the Grok Bot app or your laptop does not stop cloud work: https://docs.x.ai/grok-bot/computer-and-apps

Files, browser state, and supported sign-ins survive normal computer updates and recovery. The docs advise treating temporary directories, manually installed packages, and uncommitted application state as replaceable, and copying important results into the shared workspace at /workspace. Folders such as node_modules or a Python virtual environment are not saved and need reinstalling after an update, Recover, or Reset.

For scheduled work, Bots use routines. See our routine ideas: https://grokusecases.com/use-cases/best-grok-bot-routines

When your own computer does matter

Running commands on your local computer. This only happens if enabled and approved. Per the changelog (Oct 14), when your computer sleeps, Bots treat it as disconnected within two minutes and say so right away, and if work is meant for one of your computers that's offline, the Bot tells you instead of running it on another computer without asking. So a job that depends on your local machine needs that machine awake and connected.

Route traffic through this computer. This setting sends the Bot's web traffic through your own computer. The changelog (Oct 27) says Settings tells you when the Bot's computer is asleep and that routing reconnects when it wakes, and that the app says when your computer goes offline. If you rely on this to reach a site or network only your machine can reach, your machine has to stay online. We haven't found documentation that this is needed for ordinary tasks.

Reaching a private network. The changelog (Nov 3) notes an MCP server on a private Tailscale network needs you to connect your tailnet from the Tailscale plugin first. An earlier entry (Oct 11) said Grok Bot couldn't reach private-network MCP servers yet. Check the current docs, since this is changing.

What some owners report (unverified user reports)

In r/GrokBot, some owners describe shopping for a VPS, worrying about memory spikes on a host machine, or routing traffic through a homelab. These are user reports about their own setups. We can't confirm the causes or whether any of them were necessary, and we don't give specs or prices for them. See the threads: https://www.reddit.com/r/GrokBot/comments/1xrx5m4/ , https://www.reddit.com/r/GrokBot/comments/1xsi0gs/ , https://www.reddit.com/r/GrokBot/comments/1xrshyr/

Our reading: if you're considering a server only to keep Bots awake, test first whether the job actually needs your own machine. If it runs entirely on the Bot's computer, a server adds cost and risk without helping.

A 10-minute test before you rent anything

1. Pick one small routine or task. Ask your Bot where it runs: on its own computer or on your local computer.

2. If it says its own computer, close the app and let the job run. Check Run history or the chat on your phone afterward.

3. If it needs your local computer, decide whether that's worth keeping a machine awake. Don't give a Bot local access you wouldn't give a new assistant, and keep per-command approval on until you trust a specific job.

4. Save anything important into /workspace on the Bot's computer, and keep your own backups of files that only exist on your machine.

5. If a Bot stops reporting, retest before you rebuild: https://grokusecases.com/use-cases/grok-bot-not-replying-fix

Security notes before you add a server

The docs say the computer is assigned to your account, not to a single Bot, so don't place a credential or file on it that another Bot on your account shouldn't use.

A separate always-on machine you control is an extra place for secrets to live. If you add one, apply the same approvals discipline as on your own computer: https://grokusecases.com/use-cases/grok-bot-security-approvals

This guide is independent and unofficial. It isn't affiliated with or endorsed by xAI, X, Grok, or Cursor, and it isn't security advice for your specific setup.