Grok Bot computer use means every Bot gets its own computer in the cloud, with a browser and a desktop, that it clicks, types and signs in on while you watch or take over. You hand it a job, it works the screen, and it stops for your approval before anything it can't undo.
📺 Watch: NEW Grok Bot is INSANE! (Everything It Can Do)
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
That is a different design from agents that drive your own laptop. Below: how the cloud computer works, the controls you get, what xAI changed in the last two weeks, and where it still falls short.
How Grok Bot computer use works
Grok Bot is xAI's team of AI agents, launched into public beta on 11 August 2026. xAI has operated as SpaceX AI since the July merger. Each Bot runs on its own cloud machine with its own screen and browser, so the work keeps going when your laptop is closed. All version dates below come from the official changelog at x.ai/changelog/bot.
The flow looks like this:
- You ask a Bot to do something in a website or app.
- If a plugin covers that app, the Bot uses the plugin. If not, it opens the browser on its own computer.
- You can watch the computer view live while it works.
- When it needs you, for a sign-in or a code, it hands the computer over. You take control, finish the step, and hand it back.
- Before it sends, posts, buys or deletes, it asks for approval.
Since v0.75.2 on 22 October 2026, the Bot tells you up front when a browser or desktop task will take a few minutes, and a browser sign-in waits up to 20 minutes for you.
If you want an agent setup you run for your own business, with daily walkthroughs as tools like this change, the AI Profit Boardroom ($69/mo) includes the Agent OS, a 30-day AI agent roadmap, weekly coaching calls and the prompt library.
📺 Watch: Hermes Bot Mode DESTROYS Grok Bot? (FREE!)
The controls that keep it safe
Handoff and takeover
Takeover is how you sign in without giving the Bot your password in chat. In v0.77.0 on 26 October, xAI added security-key sign-in during takeover. In v0.75.5 on 23 October and again in v0.77.0, xAI made the Bot offer the matching connector instead when it hands you its computer to sign in to Google, GitHub or QuickBooks. A connector is usually faster and more reliable than clicking through a login screen.
Secure Forms
Secure Forms collect sensitive details without the Bot reading them out in chat. In v0.68.1 on 7 October, Secure Forms began filling straight into the page, and checkout card fields got a Secure Form instead of a full screen handoff. In v0.71.2 on 14 October, the Bot started asking only for missing fields or a verification code in a Secure Form at checkout.
Approvals
Since v0.70.2 on 11 October, before an action it can't undo (sending, posting, buying or deleting), a Bot checks your own messages for approval. Purchases still show a card with the amount to Allow or Deny, a flow that started in v0.30.0 on 28 August.
Route traffic through this computer
Some sites only trust your own network. Grok Bot has a "Route traffic through this computer" setting, documented in xAI's private networks docs, that sends the Bot's traffic through a member's own desktop. That helps with sites that block cloud IP addresses or tools that sit on your office network.
Team and enterprise controls
On enterprise plans, xAI lists a Terminate Inactive Computers option for machines idle for 30 days, admin controls to delete VMs and data, and Team Setup scripts that receive Team Secrets as environment variables. Action Recording redacts card numbers and tokens.
📺 Watch: OpenMausBot DESTROYS Grok Bot?
What changed recently in v0.77.0 and v0.78.1
The last two releases were mostly about making the cloud computer more stable and more human-like.
v0.77.0, 26 October 2026
- The Bot's computer stays up when memory runs low and recovers faster after a crash.
- Install prompts finish instead of hanging.
- The browser keeps site logins.
- Screenshots of tall pages are full size.
- Security-key sign-in works on takeover.
- System keyring keys survive when the computer is recreated.
v0.78.1, 27 October 2026
- The browser types one character at a time and moves the mouse on every website it fills in.
- The computer view follows whichever tab the Bot brings to the front.
- Approved browser actions no longer fail when the page hasn't changed.
- Reset and Recover keep the current disk, so you don't lose files when you fix a stuck machine.
The typing change matters most. A form that fills in all at once looks like a bot. Typing and moving the mouse like a person is xAI's answer to that.
Want to know whether a cloud computer agent like this fits your workflow? Book a free AI strategy session and we'll look at the jobs you want to hand off.
Grok Bot computer use vs local computer use
| Area | Grok Bot | Local agents (for example Codex computer use) |
|---|---|---|
| Where it runs | The Bot's own cloud computer | Your own Mac or Windows PC |
| Works with laptop closed | Yes | No |
| Your logins | Takeover, connectors, Secure Forms, Vault | Already signed in on your machine |
| Network | Cloud, or route through a member's desktop | Your own network |
| Risk to your files | Separate machine | Can touch your own apps and settings |
| Recovery | Reset and Recover keep the disk (v0.78.1) | Your own machine state |
OpenAI's docs say Codex computer use runs in the ChatGPT desktop app on macOS and Windows through a plugin, with Screen Recording and Accessibility permissions. The full comparison is in Grok Bot vs Codex.
Limits to know before you rely on it
It is slow. Screen-by-screen work takes minutes, and xAI's own changelog now warns you when a task will take a while.
It can fail on simple jobs. When I tested Grok Bot the day after launch in August, the onboarding was excellent, but its computer use failed on a simple task: open Google and type hello. It crawled screenshot by screenshot and got stuck. The full test is in Grok Bot vs Hermes. Many fixes have shipped since, but that is the result I saw.
Plugins beat clicking. xAI keeps pointing the Bot at connectors over the screen, from the sign-in handoffs in v0.75.5 to the sign-in pages that offer a connector in v0.78.1. If an app has a plugin, use it. See Grok Bot plugins for that side.
Plans and usage. Heavy computer use runs long tasks, and the Usage and Billing page has shown weekly usage and a monthly on-demand limit since v0.46.0 on 9 September. Check it before you schedule a lot of browser routines.
If you want to compare agents on the same task rather than on demos, the Goldie Bench does exactly that. And if you want an open setup you own, with Hermes Agent and no metered cloud desktop, start with the Agent OS guide.
Need help picking the jobs worth automating first? Grab a free AI strategy session and leave with a plan.
FAQ
Does Grok Bot use my own computer?
No. Each Bot has its own computer in the cloud. You can route its traffic through a member's desktop with the "Route traffic through this computer" setting, but the Bot still works on its own machine.
Can I watch and stop what the Bot is doing?
Yes. You can watch the computer view live and take over at any point. Since v0.78.1 the view follows the tab the Bot brings to the front, so you see what it sees.
Is it safe to let Grok Bot sign in and pay?
The Bot asks for approval before actions it can't undo, uses Secure Forms for card details and verification codes, and offers connectors for sign-ins like Google, GitHub and QuickBooks. You still approve every purchase.
How do I start using it for my business?
Pick one browser job you repeat every week and test it with approvals on. For a guided setup, join the AI Profit Boardroom, or book a free AI strategy session.
