AI ·
Grok Bot
Always-on agents with a computer of their own, announced 11 August 2026. What that product is, and what @grok on X is.
Two things wear this name. They share a family, and they are different products. Mixing them up makes the rest of the conversation nonsense, so the split comes first.
@grok on X is the public assistant. You mention it in a post, or you open the Grok app, and it answers in the conversation. It is Grok, the chatbot, sitting where the people are. The account has been there since the product launched in 2023.
Grok Bot, announced on 11 August 2026, is a teammate. The line on the launch post is a team of always-on agents, with their own computer, working inside the tools and apps you already use, including overnight. xAI had been running it internally. On that date they opened a beta. The design essay from 3 September 2026 is the companion piece: a roster, a presence, and work that can start without a fresh prompt.
What "a computer of its own" changes
An agent in a browser tab dies when you close the lid. Grok Bot is described as a machine in the cloud. It can sign in to a site, including a site that has no API and no MCP server, and it keeps going when you leave. The finished work is supposed to land where a person would have put it: the CRM note, the draft in the inbox, the ticket in the tracker.
That is a real difference, and it is the whole product. A chat that is 90 percent done is a draft on your screen. A bot that is 100 percent done has already touched the system of record. The second one is more useful. It is also the one that can do the damage if the task was underspecified or the page it read was poisoned.
You message it the way you message a colleague, from the phone or the desktop, and the thread is the same thread later. The pitch is that you do not draw a workflow first. You hand over a job in a sentence. I believe the sentence, and I still write the sentence carefully. "Handle the inbox" is not a job. "Draft replies to the five unread messages from paying clients, in my usual length, and leave them as drafts" is a job.
A small team, not a pile of tabs
The launch describes running several bots at once. One sits on top, and specialists take lanes: the inbox, expenses, a bug, the ops queue. They can message each other and share a thread, so you are not the pastebin between two windows. They can sit in a group chat, pass work, and pull you in for a judgment.
On 28 September 2026, Team Bots extended that to an organization: shared teammates that more than one person can direct, and that keep what they learned. A personal bot and a team bot are different trust decisions. The personal one knows your voice. The shared one knows the company's, and it will be wrong in public if you let it send.
Showing the work once is the training method they emphasize. You do the job while the bot watches, it stores a routine, you correct the routine, and next time it runs. That is programming by demonstration, aimed at office work. It is powerful on a process you can recognize when it drifts. It is a poor fit for a process you cannot check, because the bot will faithfully repeat the drift.
The calendar, briefly
- 11 August 2026. Launch. Beta for SuperGrok, SuperGrok Plus, SuperGrok Heavy, and several Cursor plans, on desktop and iOS. Usage is counted apart from the chat plan, so a handoff does not spend the allowance you use for conversation.
- 26 August 2026. The plan list widens. SuperGrok, Cursor Pro, and Cursor Teams are in.
- 29 August 2026. A tighter integration with X.
- 3 September 2026. Enterprise, and the design essay.
- 28 September 2026. Team Bots.
Internal write-ups from the same season are worth reading as anecdotes with numbers attached, not as your forecast. One describes the support operation moving onto bots. One describes a procurement pass that found more than $100,000 of spend. Those are their stories about their own company. A buyer's question is whether the same shape fits a process you can audit.
What I will hand it
A draft I am going to read. A triage that ends in a list, with send still on me. A check of a spreadsheet that a second person looks at. A routine I have watched once and can spot when it goes strange.
What I will not hand it on the first week, and maybe not on the tenth: a credential I cannot revoke, a customer message that leaves the building unsent-by-me, a payment, a merge to a branch other people deploy. The computer of its own is the feature. It is the reason the permissions stay narrower than the prompt. Trust is a dial you move after you have seen the work, not a setting you flip because the launch post was confident.
Grok Build is the agent for a repository, while you are there. Grok Bot is the agent for the rest of the desk, while you are not. I want both. I want them on different keys.