Grok Bot gives you AI teammates, called Bots, each with a name, a job, and a persistent cloud computer with a browser, filesystem, and terminal. According to the Grok Bot documentation, that computer lets tasks finish in your real tools instead of as chat drafts.
Most AI assistants hand you a draft and leave the rest to you. Grok Bot is built to finish the work. I’ve been using it to run recurring marketing tasks, and this site is one of them. Here is what Grok Bot is, how it works, and the Bots I actually use.
What is Grok Bot?
Grok Bot is an app from the team behind Grok. You work with a Bot by messaging it: type, dictate, or start a voice chat. Give it a task, the context, and access to the tools it needs, and it takes on multi-step work across apps and websites, then comes back when something needs your approval.
All of your Bots share one cloud computer, including its files, browser sessions, and app logins, so handoffs between Bots don’t require repeating setup. Bots use connectors where they exist and operate a browser for everything else. The launch announcement highlights that Bots can work on platforms with no clean API.
The desktop app runs on macOS, Windows, and Linux, and there is a mobile app for iPhone, iPad, and Android. Because the computer lives in the cloud, work continues while your laptop is closed.
Access and plans
As of October 25, 2026. There is no standalone Grok Bot plan; access is bundled into other subscriptions. The documentation lists every paid individual Cursor plan, the Cursor Teams plan, and linked SuperGrok, SuperGrok Plus, and SuperGrok Heavy subscriptions, and Cursor’s docs add Grok Business seats. Since October 18, 2026, Grok Bot is part of The X Subscription in its Premium, Super, and Ultra tiers, and it shares one weekly usage pool with Grok and Cursor, according to the Grok Bot plans help page.
The eligible plans have changed several times this year, so treat this as a snapshot and check the official Grok Bot page before you buy.
What’s new in October 2026
Four releases from the past week matter for marketing work. Each one cuts a step that used to need you.
Pages
October 21, 2026
A Bot can write a live document or app, like a report, dashboard, or plan, and keep updating it as you ask. Pages sit in the Bot’s Library. You can keep one private, share it with your team, or share it with anyone who has the link. To change one, you ask the Bot.
Vault
October 22, 2026
Cards, logins, and personal details live in one place, and Bots fill checkout and sign-in forms from there. You stop pasting card numbers and passwords into chat. Only you can see what’s saved.
Password manager sign-in
October 22, 2026 (rolling out)
A Bot can sign in to sites with logins from your password manager. You approve each request in the password manager’s app, and the Bot never sees the password.
One-press voice
October 19, 2026
On newer phones with a programmable side button and the 1.16 app, one press starts a voice chat with a Bot. It’s the quickest way I’ve found to hand off a task while away from my desk.
For marketers, Pages is the big one. A client report or campaign plan used to be a file you rebuilt each month. Now it can be a link the Bot keeps current.
How Bots work: skills, routines & handoffs
One Bot per job
You create multiple Bots, each with its own assignment, and they run in parallel. Setup is a message, not a workflow builder. A named Bot keeps its memory, files, and preferences across sessions instead of resetting on every task.
Skills and routines
Grok Bot uses two building blocks. A skill is a reusable set of instructions for how to do a task. A routine tells one Bot when to run a workflow, on a schedule or, where supported, after an event such as a Slack message or a GitHub notification.
You can also teach a skill by demonstration. The Work with Grok Bot guide describes a Teach a task option that records you performing a browser workflow and turns it into a draft skill. Its recommended order: start with a one-time task, make it reliable, save the method as a skill, and only then automate it with a routine.
Handoffs and group chats
Bots can message each other, share context in group chats, and pass ownership of a task, so you aren’t the router between tools. Team Bots go a step further: you give a Bot the files, apps, and expertise it needs, then share it so your whole team works from the same context.
Approvals and safety
When an action needs approval, the conversation shows the proposed operation and its inputs. According to the approvals documentation, you can choose Allow once, Always allow (which can save a matching rule), or Deny. An approval request from work that started without you, such as a routine, expires after about 10 minutes and the action doesn’t run.
Behind those prompts is Auto Review, an independent review model that evaluates risky actions before they run. It can let an action proceed, require approval, or deny it. The docs say it complements, rather than replaces, explicit approval boundaries.
The documentation’s own checklist is good advice for marketers:
| Connect only what’s needed | Give each workflow only the tools it requires |
|---|---|
| Start read-only | Begin with read-only tasks and draft outputs |
| Gate the big moves | Keep sending, publishing, purchasing, deletion, and production changes behind approval |
| Review regularly | Check installed connectors and active routines, and pause a routine when its source changes |
From my experienceMy website Bot drafts the change, publishes a private preview, and waits. Nothing goes to production until I say yes.
How I use Grok Bot for marketing
Here are the nine Bots I run today. Each one has a single assignment.
| Bot | Area | What it does |
|---|---|---|
| LLM Brand Visibility Check | Research & intel | Checks how AI assistants describe and recommend a brand |
| CRM Vendor Release Updates | Research & intel | Tracks CRM vendors’ changelogs and release notes for news worth writing about |
| New IRS Tax Credits | Research & intel | Watches for new IRS tax credits, a niche topic I follow |
| Find CRM Selection Leads | Lead gen | Looks for companies that appear to be evaluating CRM software |
| New Lead Research & Fit Analysis | Lead gen | Researches a new lead and assesses fit with our services |
| My ClickUp Tasks | Ops & content | Reviews my ClickUp tasks through the ClickUp connector |
| Social Campaign Reminders | Ops & content | Keeps a social campaign on schedule with reminders |
| Manage Static Website | Website | Maintains helpfulseos.com (case study below) |
| Fictional Restaurant – Website Updates | Website | A practice site for testing website update workflows |
The LLM Brand Visibility Check Bot is the same idea behind our AI brand visibility check, and it pairs naturally with brand name optimization.
Case study: the Manage Static Website Bot
The Bot I rely on most maintains helpfulseos.com. The site is static HTML hosted on Netlify, an approach I covered in setting up a static website for speed and savings.
Here is what it did on its first assignment, and where I stepped in:
1. Copied the site. With my approval, it copied the site folder from my Mac to its own cloud computer.
2. Connected to Netlify. It installed the Netlify command line tool, and I signed in once.
3. Converted a WordPress post. It rebuilt Rethinking WordPress Featured Image Size & Style for AI Overviews/Mode as static HTML matching the site’s template, including images, structured data, the blog index, the sitemap, and a cleaned-up redirect.
4. Previewed it. It published a draft deploy to a private preview URL for me to review.
5. Published it. After I approved, it went live in production.
6. Synced back. It copied the changed files back to my Mac after checking that my local versions hadn’t changed in the meantime.
UpdateI’ve since stopped syncing files back to my laptop. The Bot’s computer and the host now hold the only copy that matters, so there is one less thing to keep in step.
Since then, I’ve given the same Bot SEO skills from a skills repository and used them on the site:
A font change. It switched body text to Inter on every page, previewed it, and published it after I approved.
A title and meta audit. It audited all 12 page titles, recommended fixes, and applied the ones I approved.
A content refresh. It ran a search gap analysis on What Is Google Page Experience & Why It Matters and rewrote the post from that plan.
Each change went to a preview first. This post was produced and refreshed the same way. I wrote up the whole setup in using an AI assistant as a headless CMS for a static site.
Creative ways I use Grok Bot
Past the case study, here is what my website Bot has taken on in the last few weeks. Every item went through the same preview-and-approve loop.
steps in each blog refresh, from request to publish
lowest text contrast after re-shading every post
internal links mapped across 16 pages and posts
daily checks for new contact form entries
The publish loop
I ask for a change
One message in chat, such as “remove the animated section from the blog page.”
The Bot edits the site
It changes the static HTML files on its own computer.
It posts a private preview
I get a draft link to review on my phone or laptop.
I say “publish”
Only then does it deploy to production and check that the live page loads.
The same Bot moved my old blog posts from a database-driven CMS into static HTML and kept every URL, so no links broke. I covered the reasons in using an AI assistant as a headless CMS.
Blog refreshes, visuals, and accessibility
| Task | What the Bot does | My part |
|---|---|---|
| Blog refresh | Rewrites stale sections, adds stat highlights, tables, step cards, and callouts, adds a new featured image and internal links, fixes broken external links, adds a fitting call to action, and updates the blog index and sitemap | Approve the preview |
| Accessibility | Re-shaded tables of contents and panels on a white background and measured the contrast of every shaded text block | Pick the look |
| Diagrams | Draws 16:9 workflow images for the site | Edit the wording |
| Link map | Built a Page showing every page and post, with arrows for each internal link | Choose which orphan posts to fix |
| Homepage | Rewrote the homepage from a Page’s content and kept the customer testimonials word for word | Approve the copy |
| Contact form | Added a form that creates a tagged contact in a CRM, with the message saved as a note | Decide which fields to ask for |
The link map is a good example of Pages at work. It showed two posts that nothing linked to except the blog index, which gave me a to-do list. Internal links help readers and search engines in the same way, a point I made in what Google page experience covers.
Housekeeping routines
Two routines run without me. A weekly job deletes old deploys but keeps the live one and the five newest of each kind, then checks that the site still loads. It only messages me when it deleted something. A second routine looks for new contact form entries four times a day and posts them in our chat, so I don’t need a separate email alert.
The Bot also added a small visitor tracker to my sites, and it runs next to the analytics script I already had. I can ask the Bot for visitor numbers in chat instead of opening a dashboard.
TipStart a routine in quiet mode. Have it report only when something changed, or you will learn to ignore it.
Ideas from the official marketing guides
The Grok Bot team has published its own playbooks, written for larger teams than mine:
Grok Bot for Marketing describes six Bots covering research, positioning, Google Ads campaign shells, landing pages opened as pull requests, and analytics, plus a Project Manager Bot. Its advice: stand up one specialist for one job, connect only the tools that job needs, and add a Project Manager after the handoffs hurt, not before.
Grok Bot for Performance Marketing starts with reporting, since reporting asks are the first questions a new initiative gets, and finds that a Bot that knows one ad platform well beats one trying to cover everything.
The use cases page lists marketing roles such as an SEO / AEO Auditor, Newsletter Writer, Marketing Calendar Owner, and LinkedIn Campaign Manager.
Team Bots describes a Marketing Bot that reviews drafts against brand guidelines in Slack and takes approved website and SEO changes from review to a preview link for final sign-off. That is close to how my website Bot works, at a smaller scale.
Grok Bot vs. a chat assistant
| Typical chat assistant | Grok Bot | |
|---|---|---|
| Where work happens | In the chat thread | On its own cloud computer, inside your apps and websites |
| Output | Drafts you finish yourself | Finished work in your tools, with drafts held for approval |
| Memory | Often starts fresh | A named Bot keeps memory, files, and preferences |
| Timing | Only while you’re chatting | Parallel, scheduled routines, even with your laptop closed |
| Consequential actions | You take them | The Bot asks first |
The Grok Bot column summarizes the product page FAQ and the documentation.
Getting started
The getting started guide walks through five steps:
1. Check your plan. You need an eligible subscription (see above).
2. Install and sign in. Download the desktop app and sign in with your Cursor account.
3. Create your first Bot. Pick a suggested teammate or create your own and describe its job.
4. Give it a first task. Type it, or dictate it.
5. Sign in to the tools it needs.
TipPick one recurring task that eats an hour or two each week, such as competitor monitoring, lead research, or website updates. The docs suggest a first task that spans a few tools and has a clear finish line. Once the result is right, turn it into a skill, then a routine.
Frequently asked questions
Can a Bot sign in or pay without seeing my passwords or card numbers?
Yes, with the October 2026 releases. Vault stores cards, logins, and personal details so Bots fill forms from it, and only you see what’s saved. The password manager integration, still rolling out, lets a Bot sign in after you approve each request in that app, and the Bot never sees the password.
Who makes Grok Bot?
Grok Bot comes from the team behind Grok. Its documentation lives at docs.x.ai, and the computers Bots work on run in Cursor’s cloud.
Does Grok Bot keep working when my laptop is closed?
Yes. According to Grok Bot’s documentation, work runs on the cloud computer, so closing the app, your laptop, or your phone doesn’t stop a background task or a routine.
Can several Bots work at the same time?
Yes. Bots can work in parallel. Each Bot gets its own screen on the shared computer, and one Bot runs one computer-use task at a time.
Can a Bot use any website?
Bots can use many browser-based tools, including services without a connector. A site can still block automation, expire a session, or require a human step, and the Bot hands those steps to you.
How much does Grok Bot cost?
There is no standalone Grok Bot plan. Access is bundled into certain subscriptions, and the eligible plans changed several times in 2026. Check the official Grok Bot page for current options.
The bottom line
Grok Bot doesn’t replace marketing judgment. It gives you teammates that handle the repetitive, multi-step work, and that come back to you when a decision is needed.
For a small marketing operation, that is a meaningful amount of time back.