agentos.guide › blog

Grok Bot Windows: Install The PC App And Run It Beside Your Agent OS

By Julian Goldie · 2 November 2026 · agentos.guide

Grok Bot Windows slots into your Agent OS as the cloud worker you steer from a PC, while your local agent keeps the files and tools that never leave the machine.

xAI's Get Started guide lists the desktop app for Windows on x64 and Arm64.

Below is a quick start, five prompts you can paste straight into your agent, and a weekly routine that keeps both sides tidy.

If you want my team to map which jobs go where, book a free SEO strategy session.

How Grok Bot and your Agent OS split the work on one PC

The deployment docs say Bots work on a hosted Linux computer in the cloud, one per member.

Your Windows PC only runs the app for chat, review and approvals.

Your Agent OS, by contrast, can sit on the PC itself with your local files and scripts.

So the clean split is simple: web research, browsing and long jobs go to Grok Bot; anything that must stay on the PC stays with your local agent.

Quick start in five moves

1. Check your plan: Premium, Super or Ultra include Grok Bot and Plus doesn't, per Grok Bot on The X Subscription.
2. Download the x64 or Arm64 Setup .exe from cursor.com/download/bot, x.ai/bot or the dashboard's Download Grok Bot row.
3. Run it; it installs per user under %LOCALAPPDATA%\Programs.
4. Sign in with your Cursor account and let it create your first Bot.
5. Open Settings → Computer → Your computer and set Execution on this computer to Never allow.

Step five matters most for an Agent OS user: your local agent already owns the PC, so Grok Bot doesn't need to.

Watch the first command card, too: Always allow or Never on it changes the setting for every Bot, while Allow once and Deny once answer only that request.

Rolling it out to staff PCs? The deployment page documents a silent install with /S, run in each user's context rather than as SYSTEM.

The approvals docs back that up, advising Never allow for any Bot without a clear need for your local files.

Prompt 1: confirm the right Windows build

Give this to your local agent before you download anything.

Check this Windows PC and tell me:
1. Is the processor x64 or Arm64?
2. Which Grok Bot installer matches it: the win32-x64 or win32-arm64 Setup .exe?
3. Is there already a Grok Bot folder under %LOCALAPPDATA%\Programs?
Only read system info. Don't install or change anything.

The answer tells you which of the two builds on the download page to grab.

Prompt 2: write the first Bot's job description

The get-started guide says to give each Bot one primary job and ask it to remember how to work.

Let your Agent OS draft that message from what it already knows about your business.

Write the first message for a new Grok Bot.
Give it ONE job: weekly competitor research for my business.
Include: the sources it should use, what to leave alone,
the format of the weekly report, and where it must stop and ask me.
End with: "Remember this for future work."
Keep it under 150 words.

Paste the result into the Bot's chat as its first message.

🔥 Get the full Agent OS for your PC

Inside the AI Profit Boardroom you get the installable Agent OS, step-by-step video trainings, four coaching calls a week and 3,400+ members wiring agents together.

→ Join the AI Profit Boardroom

Prompt 3: draft your approval rules

Grok Bot asks before actions it can't undo, and you can add Ask first rules on top.

Have your agent turn your business rules into plain-English rules you can paste in.

Read my notes on what an assistant may and may not do for my business.
Turn them into a short list of "Ask first" rules for Grok Bot:
- anything that sends email or posts publicly
- anything that buys or subscribes
- anything that deletes files
Write each rule as one sentence I can paste into Custom Rules under Settings, Bot.

Keep the list short so every rule gets read.

Prompt 4: the weekly version check

The troubleshooting guide says the app demands an update once your version is more than 14 days old and a newer one is out.

A weekly reminder stops that screen from catching you mid-task.

Every Monday at 9am, remind me to:
1. Open Grok Bot, account menu, Support, About, and press "Copy version info".
2. Paste the version here so you can log it.
3. If Settings, Updates offers "Restart to Update", do it before starting work.
Keep a running log of versions and dates.

Remember that changelog v0.59.0 means a downloaded update on Windows also installs when you quit.

Prompt 5: back up what the cloud doesn't

Files that exist only on your Windows machine aren't covered by the Bot computer's recovery.

Your local agent is the right one to fix that.

List the folders on this PC that hold work files Grok Bot has helped with
(downloads of its reports, exported drafts, client folders).
Propose a weekly backup plan for them to my usual backup location.
Show me the plan first. Don't copy or delete anything until I say yes.

Approve the plan, then let it run on a schedule.

Keep the backup target off the Bot's reach too, so only you and your local agent can touch it.

Prompt 6: route each new job to the right agent

The split only works if every new task lands in the right place.

Give your local agent a standing triage rule.

When I give you a new task, decide where it runs:
- Grok Bot if it needs the web, a browser, a routine or hours of work.
- You (local) if it touches files on this PC or private client data.
For Grok Bot jobs, write the brief I should paste or dictate (Ctrl+D).
For local jobs, show me your plan before you start.

After a week, review where the jobs went and tighten the rule.

A weekly workflow that keeps both agents in step

1. Monday: version check (Prompt 4) and a quick look at the Grok Bot changelog for Windows lines.
2. Tuesday to Thursday: hand web jobs to Grok Bot, dictate briefs with Ctrl+D, approve results in the Windows app.
3. Friday: your local agent files the week's Bot reports and runs the backup (Prompt 5).

Since v0.71.2, Bot replies and questions notify you on the Windows PC while you're using it, so you won't miss an approval at your desk.

When you step away, the phone picks up questions about three minutes later unless you've opened that Bot, per the settings docs.

📞 Want us to plan your agent split?

Book a free SEO strategy session and my team will help you decide which jobs go to Grok Bot and which stay in your Agent OS.

→ Book your free strategy session

Pinning one build across several PCs

If your Agent OS runs on more than one Windows machine, keep them on the same Grok Bot build.

The deployment page gives a JSON feed per architecture, win32-x64-user and win32-arm64-user, whose downloadUrl field points at the current Setup .exe.

Ask your local agent to read the feed weekly, log the version and flag when the two PCs drift apart.

Updates still arrive on their own, since nothing turns off update checks on Windows, so the log is about knowing, not freezing.

Windows settings to check once

• Use hardware acceleration: on by default since v0.67.0; switch it off and choose Restart Now if the window flickers or goes blank.
• Microphone: pick the headset your dictation should use.
• Use hardware security keys: on by default on Windows, under Settings → General → Security Key.
• 1Password: from 0.75.2 onward the Bot notices an installed 1Password app; connect it under Connect apps → Password Managers, per the computer and apps docs.

Windows Hello and passkeys on your laptop don't carry over to the Bot's computer, so a hardware key or 1Password is the smoother route.

When something misbehaves

• The app hangs on launch: fully quit and relaunch, then contact support with your version if it keeps happening.
• Pasted text looks wrong: builds from 0.70.2 onward keep list text inline and keep non-English characters and curly quotes, so update first.
• Update required covers the window: choose Update, then Restart to update; your Bots keep working in the cloud meanwhile.

Running a Mac as well? The Grok Bot Mac guide covers the Apple side of the same setup.

The AI Profit Boardroom has the step-by-step trainings for running both agents from one Agent OS.

FAQ

Should Grok Bot run commands on my PC if I already use an Agent OS?

Usually not. Set Execution on this computer to Never allow and let your local agent handle the PC, which is what xAI recommends unless a Bot needs your local files.

Which installer do I need for a Windows laptop?

The x64 Setup .exe for x64 processors and the Arm64 Setup .exe for Arm processors. Both are on cursor.com/download/bot.

How do I dictate a task to Grok Bot on Windows?

Press or hold Ctrl+D while the prompt is focused.

Will Grok Bot notifications still hit my phone?

While you use the Windows app, replies and questions notify you on the PC. If a Bot needs input and you have not opened it, your phone is notified about three minutes later.

Final word on Grok Bot Windows

Paste Prompt 1 into your agent today, install the matching build, and book a free SEO strategy session if you want help splitting the work with grok bot windows.

Related guides on agentos.guide

→ Grok Bot Linux: Install And Update It In Your Agent OS

→ Grok Bot Computer Use: A Quick Start, Five Copy-Paste Prompts And A Daily Workflow In Your Agent OS

→ Grok Bot Browser: Safe Web Tasks In Your Agent OS

→ Grok Bot Android: Approve And Steer It In Your Agent OS

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide