Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124

The new teammate is a cloud computer. That is the shortest way to explain Grok Bot without mixing it up with Grok the chatbot, ChatGPT, or the @grok account on X.
A chatbot answers you. Grok Bot is built to finish work inside the apps you already use, on a persistent machine that keeps running after you close the laptop. SpaceXAI launched it in August 2026 as named AI teammates you message like colleagues.
They sign into tools, work across inboxes and websites, and come back when a human decision is required. Read the official launch post.
Most office AI still stops at a draft. Gallup finds that U.S. workers who use AI at work mostly use it for writing, research, and problem solving. Grok Bot is aimed at the gap after that draft: CRM updates, invoice chasing, bug reproduction, scheduled follow ups. Gallup workplace data shows 52 percent of U.S. employees now use AI in their role at least sometimes, and 15 percent use it daily. The product bet here is that daily use moves from “ask a box” to “hand off a job.”
Grok Bot is a product, not a personality setting inside the Grok chat app.
You create a named Bot, give it a job, and grant access to the sites and files it needs. The Bot works on a cloud computer with a browser, files, and a terminal. Product docs describe Bots as teammates that can use apps and websites the way you do, including tools with no clean API. See the Grok Bot overview.
The output is not supposed to live only in the chat thread. The output is supposed to land where the work already lives: the CRM row, the ticket, the draft sitting in Gmail, the checklist in the product.
That is why people inside the company keep repeating the same line. There is a big difference between 90 percent done and 100 percent done. Chat gets you close. A computer can put the last piece in the actual tool.
A chatbot waits for the next prompt. You stay in the loop for every click.
A Grok Bot is meant to keep going while you are in a meeting, on a plane, or asleep. The product site says Bots run in parallel and keep working even when the laptop is closed. That claim is on the Grok Bot homepage.
The Verge summarized the same idea for a general audience: agents that work independently on a cloud computer and only return when the job is done or approval is needed. Read The Verge coverage.
A chatbot gives you language. A summary. A first draft. A list of next steps you still have to perform.
That is useful. It is also why so much “AI at work” still feels like extra homework. You asked. It answered. You still logged into five systems.
Grok Bot gives you time on a machine that can click, type, save files, and come back with a result in the system of record.
Company examples from launch include a sales Bot updating the CRM from call notes, an ops Bot processing invoices found in Gmail, and an engineering Bot reproducing a bug in the product UI then filing the ticket.
You still decide. You still approve money, customer email, and anything that can embarrass the company. The change is who does the clicking between those decisions.
No. People ask this constantly because the names collide.
Grok is the conversational assistant on grok.com, the Grok apps, and X. Grok Bot is a separate teammate product with a computer. Even Grok has said it in public: Grok is the conversational AI. Bot is the teammate that signs into tools and returns finished tasks.
Think of the model as the brain and the Bot as the desk, browser, and login session that brain gets to use.
If you only open Grok to ask “rewrite this email,” you are using a chatbot. If you tell a named Bot “find open invoices, chase the ones past due, and only ping me when a vendor disputes the amount,” you are using Grok Bot.
No. That is the point of the cloud computer.
Work happens on a persistent machine tied to your account, not on the keyboard in front of you. You can keep using your own computer while the Bot works on another instance. Launch interviews with early users stressed this: the site is open on the Bot’s machine, and the Bot has to understand how that site actually functions.
Docs also clarify a detail marketing blurbs sometimes blur. Multiple Bots share one computer scoped to your user account and can run in parallel. They can message each other and pass work. They are not separate locked vaults. Treat logins, cookies, and files as visible across your Bot roster unless the product later changes that model.
It is built for multi step office work that already happens in browsers.
The jobs that already eat coordinators, EAs, SDRs, and ops people.
Sales research overnight, then a draft sequence in your voice. Inbox triage across several addresses. Invoice hunts across portals and email. Weekly pipeline hygiene. Recruiting screens that sort a pile into strong, mid, and no. Demo environment checks before a customer call.
Those are not “write a poem” tasks. They are “open six tabs and do not lose the thread” tasks.
Anything that spends money, signs a contract, messages a customer as you, or changes production without a review gate.
The product story is “come back when you need approval.” Your job is to make approval real. If the Bot can send without you, you built a liability, not a teammate.
Gallup’s workplace research still shows most AI use clustered around writing and research, not full automation. Coding and automation users report the largest productivity gains. A Bot that only drafts is a chatbot with extra steps. A Bot that executes inside tools is closer to that automation group. See Gallup’s AI indicator.
You assign ownership the way you would in Slack.
“You own campus NDA collection. Send the packet. Nudge non responders twice. Bring me the ones who refuse.”
That is a job. “Help me with NDAs” is a chat.
Early users inside SpaceXAI described the first week as micromanagement, then trust. One ops user said they checked every 15 minutes until the Bots asked why they kept asking so many questions. That quote is in the launch article.
The practical pattern that keeps showing up among operators:
Start with one Bot that behaves like a chief of staff. Have it audit how work actually moves. Prove one workflow by walking through it once. Save that path as a routine. Only then clone a specialist Bot for inbox, research, or follow ups.
Do not dump newsletter ops, receipts, and five Slack workspaces onto one Bot on day one. Shared context turns into sludge. Token use climbs. Quality drops. One mission per Bot is the workplace version of a clean job description.
Access is bundled. There is no standalone Bot checkout for most people.
Cursor’s help docs say paid individual Cursor plans and Cursor Teams include Grok Bot. You can also grant usage by linking an individual SuperGrok, SuperGrok Plus, or SuperGrok Heavy account. SuperGrok Lite does not include it. Team and enterprise SuperGrok linking is not supported on that path. Details live on Cursor plan docs.
Usage for Bot is weekly and metered by agent steps and tokens, not by how many messages you typed. Bigger jobs drain the bar faster. After the included week, extra work can spill into on demand spend if that setting is on.
Exact weekly dollar amounts are not published. Ultra and linked Heavy sit at the top of the ladder. Pro sits lower. Check the live percentage in the plan screen rather than trusting a rumor about a fixed credit.
The product is still beta. Desktop and iOS are the supported surfaces in the public materials. Enterprise sits on a waitlist unless your admin has enabled it.
The questions match what you hear in ChatGPT style searches and in product forums. Threads about Grok still mix the chatbot brand with this new agent, which is why the naming confusion will not die soon.
No. Siri and most phone assistants try to answer or set a reminder on your device. Grok Bot is a remote worker with a browser session that can last hours.
That is the design. The cloud machine does not need your laptop awake. You still need enough weekly usage left, valid logins, and a task that does not stall on a captcha, a missing password, or a human only page.
It can take slices of that work. It does not absorb judgment, relationships, or accountability. If a customer gets a bad email, the company will not blame “the cloud.” It will blame the person who granted send access.
Long agent runs are expensive. Computer use, many tabs, and parallel Bots chew tokens. Scope the first jobs tightly. Watch the meter before you launch an overnight fleet.
Only as safe as the accounts you connect. A Bot that can open Gmail can read Gmail. A Bot that can open the CRM can change the CRM. Set an approval rule for outbound mail. Use a dedicated Bot email when you can. Do not paste production secrets into a Bot you treat like a toy.
The valuable human skill shifts from typing the work to assigning the work.
You write a clear outcome. You name the system of record. You define the stop rule. You review exceptions. That is closer to managing a contractor than chatting with a model.
Hiring will follow. “I use ChatGPT” will sound like “I use email.” “I run an inbox Bot with an approval queue and a weekly quota I can explain” will sound like operations.
The risk for companies is shadow IT. People will buy Cursor or SuperGrok so they can run Bots at home, then connect work systems without a policy. The risk for workers is the opposite: coordination jobs get thinner first. Modeling, field work, and exception handling last longer than “chase the vendor portal.”
None of that requires you to love the brand. It requires you to see the shape of the tool. A chatbot is a conversation. Grok Bot is a desk in the cloud that you can staff.
If you remember one line, remember this. The new teammate is not a better paragraph. It is a computer that keeps working when you stand up from yours.