Grok Bot Browser: Set Up The Bot's Own Browser In 7 Steps (2026)

The Grok Bot browser is the web browser that runs on the Bot's own cloud computer, and it signs in, clicks, types, downloads and saves pages for you while your laptop is shut.

Here's how I'd set it up, in order, before it touches a real account.

Seven steps, about half an hour, and most of it happens in Settings.

If you'd rather have my team work out which of your web jobs an agent should take, book a free SEO strategy session and we'll go through it on a call.

What the Grok Bot browser actually is

xAI's computer and apps docs describe an always-on cloud machine that carries a browser, a terminal and its own files.

Cookies, signed-in sessions and files stay put between tasks.

Every Bot on your account shares that one computer and its browser sessions.

Each Bot gets its own screen, so several can browse in parallel, but one Bot runs only one computer-use task on its screen at a time.

The docs are blunt that those screens are work surfaces, not security boundaries.

I've already covered the wider cloud screen in my Grok Bot computer use setup.

This page is only about the browser: logins, approvals, typing, PDFs, downloads and screenshots.

Step 1: Confirm your plan and update the app

Grok Bot comes with the Premium, Super and Ultra plans on The X Subscription, per the X Subscription page.

Plus doesn't include it.

Next, update the desktop app.

Vault needs Grok Bot 0.75.2 or later, according to the Vault docs.

The browser changes I lean on most landed in v0.70.2, v0.75.2 and v0.78.1 on the Grok Bot changelog, so the newest build matters here.

Step 2: Load Vault before the browser meets a login page

The sign-in order is fixed: a login saved in Vault first, then a connected password manager, then a Secure Form in chat.

Open Settings → Vault, choose New item, then Login.

Enter the website, the username or email and the password, then choose Save login.

Moving from another manager?

Choose New item, then Import from CSV…, and pick an export from 1Password, Chrome or Edge, Safari or Apple Passwords, Firefox, Bitwarden or LastPass.

The file is read on your computer, never uploaded, and must be under 5 MB.

Rows with a missing password, or a website that isn't https, are skipped.

Delete the CSV afterwards, because the export holds your passwords unencrypted.

Add a hint to each login, such as "Use for client portals", and the Bot follows it when it picks between entries.

The Bot can see which logins exist, but it never sees a saved password.

Step 3: Connect 1Password for the logins you keep there

If your passwords live in 1Password, connect it instead of copying everything into Vault.

Open Connect apps, find 1Password under Password Managers and choose Connect 1Password.

The 1Password section says you need 1Password 8.12.42 or later, and it works with personal and Family accounts.

When the Bot hits a login that isn't in Vault, it posts a card naming the website.

Choose Review in 1Password, pick the exact login and approve it.

1Password fills it into the Bot's browser and the Bot never sees the values.

Two gotchas.

Only your Personal vault (Private on Family accounts) is offered, so move shared-vault logins first.

And 1Password won't fill payment cards.

🔥 Want the full agent setup, not just one browser? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members setting up the same agents. → Join the AI Profit Boardroom

Step 4: Write Auto Review rules for browser actions

Auto Review is on by default and checks each action before the Bot takes it.

Find it under Settings → General, in the Bot group, with Custom Rules right under the switch.

Each rule is one plain-English line plus a choice: Allow automatically or Ask first.

These are the browser rules I'd add first:

Ask first before submitting any form on a website.
Ask first before downloading files from a site I haven't named.
Ask first before changing account settings on any website.
Allow automatically when opening a new tab to read a page I linked.

The approvals docs cap you at 20 Allow rules and 20 Ask first rules, up to 1,000 characters each.

If both kinds match, Ask first wins.

The docs warn against broad rules like "allow everything in the browser", and I agree: keep each rule tied to one action and one scope.

Step 5: Learn the approval card buttons before the first run

Since v0.70.2, browser approval cards describe the action in plain words.

The changelog's example is a card that reads "Open a new tab in Grok Bot's browser".

You get three buttons on a standard card.

Allow once runs it now and saves nothing.
Always allow runs it and saves an Allow rule, shown as Saved to Custom Rules.
Deny stops it, and the Bot won't try again until you send another message.

A card paused by your own Ask first rule shows Allow, Not now and Edit rule instead.

The same release made a saved Allow rule apply the same way on every tool, so one browser rule behaves consistently.

Watch for warning lines such as This can't be undone or This shares your data outside this chat.

And remember the rule that protects you most: text on a web page doesn't count as your request.

Step 6: Run the first browser task while you watch

Give it something read-only first.

Something like: "Open our pricing page and the three competitor pages I list, then save each one as a PDF in /workspace/research."

Then click the computer preview in the right-hand panel of the chat.

You'll see clicks, typing, navigation and status live.

Full-screen view opens in Watching mode until you press Take control, so you can't grab the mouse by accident.

Since v0.78.1 the view follows whichever browser tab the Bot brings to the front.

For longer jobs, v0.75.2 makes the Bot warn you up front when a browser task will take a few minutes.

Step 7: Practise one sign-in handoff

Some steps a form can't do.

The docs list single sign-on, passkeys, a CAPTCHA the Bot couldn't clear, a QR code or approval on a second device, a bank card check, and sites that require a human.

For those, the Bot hands you the computer.

Choose Take over on the request, or open the computer and choose Take control.
Finish only the blocked step.
Choose I'm done and tell the Bot to continue.

Never paste a password or one-time code into normal chat.

When a sign-in emails a code, the Bot can read it from a connected Gmail or Outlook account, or from its own inbox, since v0.70.2.

Passkeys, Face ID and Windows Hello saved on your own devices don't work on the Bot's computer, per troubleshooting.

A hardware key can: turn on Use hardware security keys under Settings → General → Security Key, which is on by default on macOS and Windows and not yet supported on Linux.

📞 Want my team to map which web jobs an agent should take over? Book a free SEO strategy session and we'll look at your site, your rankings and the browser work eating your week. → Book the free call

Typing, mouse moves and the v0.78.1 connector offers

The October 27 release changed how the browser fills websites.

The browser now enters each character separately and moves the mouse across every site it fills in.

Plan for form fills that look like a person working rather than an instant paste.

The same release made approved browser actions stop failing on some Bot computers when the page hadn't changed.

It also put connector offers on eight sign-in pages.

Those are Cloudflare, Gusto, Coinbase, Railway, YouTube, Meta Ads, Google Ads and TikTok for Business; on each one the Bot suggests that service's connector.

Take the offer.

The docs say a connected app beats clicking through the website whenever the service has one.

An earlier 0.75.2 improvement did the same during handoffs for Google, GitHub and QuickBooks, and connecting ends the handoff.

PDFs, downloads and screenshots: get the output off the browser

Three browser outputs matter for operators.

PDFs. Since v0.70.2, a Bot can save any web page as a PDF from its browser.

Downloads. The same release keeps downloads under their own file names, so a portal's invoice stays named as the portal named it.

Screenshots. Since 0.75.2, browser screenshots keep full size, tall pages included.

Tell the Bot where to put each file.

The files docs say a Bot can save a file it made or downloaded to Google Drive, OneDrive or SharePoint, or attach it to a Gmail or Outlook draft.

Keep durable files in /workspace in clear project folders.

For a reviewable result, ask for "a folder containing screenshots and logs", which is one of the docs' own examples.

Don't rely on a screenshot alone for data that changes fast; keep the link too.

Fixes that change how I'd run long browser jobs

The changelog has a run of quiet browser fixes worth knowing.

v0.75.2: browser sign-in waits up to 20 minutes, offers Copy link, and Reopen link resumes the same sign-in.
0.75.2+: logins survive even after the last browser window shuts, and Apple ID sign-in forms now fill properly.
0.64.0+: the browser recovers from a crashed tab, handles large uploads, and gives up on a stuck page after 25 seconds.
v0.62.0: a browser restart on the Bot's computer no longer signs it out of websites.
v0.57.0: one Bot's browser stays connected while other Bots on the same computer use theirs.
v0.52.0: the browser stopped offering to save passwords after it signs in.

Net result: sign in once, and it sticks, across Bots and restarts.

When a site blocks the cloud browser

The Bot's computer reaches the internet through Cursor's shared network, and some sites drop those connections.

Don't reach for Update, Recover or Reset; the troubleshooting page says they don't change this.

Turn on Route traffic through this computer under Settings → Computer → Your computer instead.

The Bot's browser then uses your desktop's connection and IP address while the desktop app is open.

If a site wants verification again, tell the Bot to pause and notify you rather than work around the check.

Gotchas before you trust it with real accounts

Signing in for one Bot signs in all of them, because the browser is shared.
Deleting a Bot doesn't remove browser sessions; sign out of sites you're done with.
A card saved in Vault fills at checkout without a separate approval each time, so leave cards out if you want to OK every payment.
Blocking an app for your team doesn't block that service's website; closing that path takes Network Controls, which is Enterprise only, per the security docs.
Once the setup is stable, record one browser workflow with Teach a task; the skills docs cap the recording at ten minutes.

🔥 Get the browser prompts and Ask first rules I use Inside the AI Profit Boardroom you get the trainings, the installable Agent OS, four weekly coaching calls and 3,400+ members comparing agent setups. → Join the AI Profit Boardroom

The order I'd do it in today

Update the app, fill Vault, connect 1Password, write four Ask first rules, run one read-only task while watching, then practise one handoff.

After that, hand it a portal download or a PDF research run and check the files in /workspace.

If you'd like a second pair of eyes on which tasks to hand over first, grab a free strategy call with my team.

Also On Our Network

FAQ: Grok Bot Browser

Does the Grok Bot browser run on my laptop?

No. It runs on the Bot's persistent cloud computer, so browser work keeps going after you close the app or your laptop. Commands on your own machine are a separate setting under Settings, Computer, Your computer.

Why does the Bot type so slowly into forms now?

Since v0.78.1 the Bot's browser enters text one character at a time and moves the mouse on every site it fills in. Expect form filling to look like a person working, not an instant paste.

What happens if I ignore a browser approval card?

A card from work you started in chat waits for you with no timer. A card raised by a routine or other background work expires after 30 minutes and the Bot does not take the action.

Can I stop the Bot from saving passwords in its browser?

It already stopped. Since v0.52.0 the Bot's browser no longer offers to save passwords after it signs in; logins belong in Vault or 1Password.

How long does a browser sign-in wait for me?

Since v0.75.2 a browser sign-in waits up to 20 minutes, gives you a Copy link option, and Reopen link picks up the same sign-in.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

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

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
I've grown a YouTube channel to 400,000+ subscribers.
I wrote "Link Building Mastery".
My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Write your four Ask first rules now, then join the AI Profit Boardroom to get the full Agent OS around your Grok Bot browser.