A teammate with a computer
A chat window can suggest the email. Grok Bot is built to open the tool and do the step. Bots sign into the products you use, including sites that never shipped a clean API, and they keep working after you close the laptop. They come back when a step needs your approval.
You talk to a Bot the way you would message a colleague, from the desktop app or from iOS, and the thread is the same on both. There is no workflow canvas to assemble before the first task. You create a Bot, name the job, and hand it something concrete.
At launch it was in beta for SuperGrok, SuperGrok Plus, and SuperGrok Heavy, and for Cursor Pro, Pro+, Ultra, and Cursor Teams. Usage sits on its own meter, separate from your Grok and Cursor allowance. Enterprise access started on its own path.
One computer, several specialists
All of your Bots share that cloud computer. Files, browser sessions, and app logins live on the account, not inside a single Bot. That is what makes a handoff possible: a sales Bot can leave notes where an ops Bot can pick them up, without you pasting context between chats.
It is also the rule you have to remember. A login placed on that computer is available to every Bot you run. Give each Bot a real role, and keep the roster small until the roles are obvious. xAI's docs suggest starting with one Bot that owns an outcome, and adding a specialist only when the work has a stable second job.
Bots can message each other and sit together in a group chat. You describe the shared outcome; they pass work and pull you in for the judgment calls. The pattern xAI describes internally is a coordinator plus specialists — inbox, expenses, recruiting, bugs — so you stop being the switchboard.
Show it once
The loop they want is short. The next time you do a job, ask the Bot to follow along. It watches the steps, saves them as a routine, and takes your corrections. The time after that, you hand off the outcome instead of re-explaining the clicks.
Routines can also run on a schedule, or wake up from another app, such as a Slack thread or a GitHub pull request. That is the difference between a prompt you repeat and a teammate who already knows what Tuesday looks like.
Where it fits, and where it should stop
Grok Bot fits work that lives in tools. Updating a CRM after a call. Processing an invoice that arrived by email. Reproducing a bug in the product and filing the ticket. The value is the last mile, the part most assistants leave as a draft in your chat.
It is a weak place to store the rules of your business. Pricing, permissions, payouts, and the record of what happened belong in software you control. A Bot can operate that software. It should not be the software. Start with narrow access, watch a few real runs, and widen it only after the Bot has been boringly correct.