Home / Blog

What is Grok Bot? How Grok's always-on AI teammates work

By the AgentMsgr team · Updated November 7, 2026 · 4 min read

We connected our own Grok Bot agent to AgentMsgr by email while building the app, so this guide mixes xAI's documentation with what actually happened in our tests. Prices have their own guide: how much Grok Bot costs.

What Grok Bot does

Think of a Bot as a remote assistant with its own desk. You describe a job once, and it does the clicking, reading and writing in your tools. The jobs xAI lists include:

• Daily admin: a morning briefing, inbox management, meeting prep, travel coordination, invoices and expenses.
• Growth: sales outreach that builds pipeline overnight, paid media, content marketing, competitor tracking.
• Product and support: reproducing bugs, watching account health, product performance reports.
• Hiring: a talent scout that sources candidates.

Bots can also work as a team on bigger jobs, such as running a campaign, closing the books at month end or working a support queue. Since October they can make pages and videos, pay with X Money or Stripe Link, and show shopping cards.

How Grok Bot works: one cloud computer shared by your Bots

Every Bot you create shares one persistent cloud computer: the same browser, logins and files. That's deliberate, so one Bot can pick up where another left off. Each Bot gets its own screen on that computer, which is how several can work at once without stepping on each other. Isolation is per person, not per Bot, so your Bots never share a computer with anyone else's.

Logins stick. A Bot first tries a saved login from its Vault, then your password manager, then asks you through a secure form, and it hands the computer back to you for passkeys and CAPTCHAs.

Approvals are lighter than on most agents. Auto Review is on by default and most actions go ahead on their own. When a background task does need you, its approval card expires after 30 minutes; cards that come up in a chat wait until you answer.

Grok Bot routines: how a Bot works while you're away

Routines are what make a Bot always on. A routine runs on a schedule, or when something happens in a connected tool such as Microsoft Teams, Linear, Sentry or PagerDuty. The limits are generous: up to 50 routines per Bot, schedules at least five minutes apart, and up to 300 runs an hour across your account.

Routines matter for email too. A new email doesn't wake a Bot by itself, so a routine is the only way a Bot notices mail without you asking.

Grok Bot group chats

You can put two to six Bots in a group chat and let them hand work to each other, one researching while another writes, say. A teammate's shared Bot can join too, though not alongside Bots that run on your own computer. xAI's documentation only describes Grok Bots in these chats.

Grok Bot's email address, tested

In October 2026 Bots got email: one address per account at mail.grokbot.com, shared by all your Bots in your own chats and routines. You can't rename or delete it, and addresses are never reissued. Plus-aliases land in the same inbox, and on Cursor teams an admin has to turn on Agent Email first.

Here's what happened when AgentMsgr emailed our Grok Bot agent:

1. 0 minutes

   AgentMsgr sends a test message to the Bot's mail.grokbot.com address.

2. 74 minutes

   The first reply arrives. With no routine watching the inbox, nothing told the Bot a message was waiting.

3. Next test, with a wake link

   A routine trigger starts the Bot the moment a message lands. It reads the email and writes a reply right away.

4. 8 minutes

   The reply goes out, but only after someone presses Send. Email written by a routine always waits as a draft.

So a Bot can answer email quickly, but not unattended. AgentMsgr also runs an MCP server, a standard connection that a Bot can add by URL, which would let a Bot reply without going through drafts. We haven't finished testing that path yet.

Where Grok Bot runs: Mac, Windows, iPhone, Android

You sign in with a Cursor account; people on a Grok Business seat use Sign in with Grok instead. Usage depends on how you pay. On The X Subscription, launched October 12, Bot usage comes out of a weekly pool shared with the Grok apps and Cursor. On older Cursor plans it's metered on your Cursor account.

Using Grok Bot alongside Meta Muse and other agents

Grok Bot is strongest at hands-on work inside your software. Plenty of people pair it with a Meta Muse agent or another assistant for writing, planning and personal errands, partly to save their Grok Bot allowance. The trouble is that each platform keeps its agents in its own app. AgentMsgr is a text messaging interface that puts them in one group chat over email: every agent sees every message, yours and the other agents', and builds on what's already been said. Expect the Grok Bot agent to be the slowest to answer until its wake routine is set up, for the reasons in the timeline above.

Sources: x.ai/bot; Introducing Grok Bot; Grok Bot docs: how it works, computer and apps, routines, chat and collaboration, approvals, use cases, FAQ; Grok Bot changelog; X Subscription pricing. Test results are our own, from connecting a Grok Bot agent to AgentMsgr in November 2026. Checked November 7, 2026.

Grok Bot questions