Grok Bot is SpaceXAI's always-on agent product, launched on 11 August 2026 as "AI teammates you can give real work to". Each account gets a cloud Linux machine, shared by every bot you create, and the bots sign into your tools, run routines and keep working while you are away. muti is a room around the coding agent already running on your own computer, where the people you invite send it work and you approve what runs.
Both want an agent to be a colleague. Grok Bot gives you many bots and one machine in the cloud. muti gives many people one agent, on a machine you already own.
What is Grok Bot?
Grok Bot comes from SpaceXAI, which is what xAI publishes as since its merger with SpaceX. Launch coverage called it "your team of always-on agents that have their own computer, work inside tools and apps like you do, and keep working 24/7". The machine has a browser, a file manager and a terminal. Bots work in places with no clean API. According to Reworked, around 220 plugins were available at launch, covering Google Workspace, Slack, Microsoft 365, Salesforce, Notion, GitHub and Jira.
Beyond that basic setup, four things stand out:
- Teach a task. You record a demonstration of up to ten minutes, and it becomes a reusable skill.
- Routines. A routine runs on a schedule or, where supported, after an event. "Background routines can run while your laptop is closed."
- Several bots at once. Bots can run in parallel, message each other, sit in group chats and report to a manager bot.
- Your computer, if you allow it. A setting of Ask every time, Always allow or Never allow lets bots use your own computer.
Grok Bot runs on desktop, iOS and Android, and from 22 September in Tesla cars for SuperGrok Heavy subscribers. It is included with SuperGrok and Cursor plans, with separate usage limits. An enterprise edition with access, network and audit controls launched on 3 September.
What is muti?
muti leaves the agent where it already works. Claude Code or Codex keeps running on your computer, with the repository checked out, the tools installed and the subscription paid for. A small daemon polls muti over outbound HTTPS, runs each request locally and streams a timeline into a room: messages, tool-call summaries, approvals and artifacts. The room never holds files, environment variables or keys. See what the daemon uploads.
The people you invite open a browser tab or message the agent's Slack bot. Each person has their own permission: read-only, edit, or a standing grant. Four kinds of action stop for you whoever asked: pushing to a shared branch, deleting, spending money and touching credentials. Every request has an id and leaves an audit line.
Grok Bot: several bots share one cloud computer on one account. muti: several people share one agent on the owner's computer, through the owner's approval.
Side by side
Where is Grok Bot the better answer?
When the work is operations, not engineering: triaging an inbox, updating a CRM, chasing invoices, filling in portals that have no API. In those cases a cloud computer that never sleeps is exactly right. Routines that run at 3 a.m. while your laptop is in a bag are something a local agent cannot offer, and teach-a-task makes it quick to hand over a workflow. If you already pay for SuperGrok or Cursor, it costs nothing extra to try.
If you want that shape but self-hosted, Rakazo describes itself as an open-source alternative to Grok Bot, with sandboxed computers you run yourself.
Where is a room the better answer?
When the capability you want already lives on one person's laptop, and the problem is that only they can use it. A coding agent with the monorepo checked out, the database reachable and the design tool logged in is hard to rebuild on a cloud machine, and it would mean moving credentials that belong where they are.
A room is also the better answer when the people asking are not the owner. Grok Bot's bots all belong to one account, and its approvals go to that account's owner about that owner's requests. In a room, requests come from other people, and the owner is always the one who says yes to anything irreversible. See borrowing an agent.
What does "security boundary" mean in each?
Grok Bot's documentation is admirably direct: "Do not use separate Bots as a security boundary." All the bots on an account share one machine, so a restriction on one bot does not isolate it from the others. The boundary is the account. The docs also warn that "an approval controls the proposed action. It does not reverse work already completed."
In muti the boundary is the room and the person. An invite gives someone access to one room, with one permission, on agents the owner chose to put there. Nothing in the room can reach another room, and nothing in any room can read the machine's keys, because they never leave the machine. The four action types cannot be made silent by any template, for any person. See zero sharing by default.
Frequently asked questions
Is there an open-source Grok Bot alternative?
Rakazo, from the author of Inbox Zero, describes itself as one. It is Apache 2.0 and self-hosted, with sandboxed computers on Docker or cloud providers. muti is not a Grok Bot clone. It shares the agent you already run rather than creating new bots with their own computers.
Can Grok Bot use my own computer?
Yes, if you allow it. Grok Bot's settings let bots access your computer on an Ask every time, Always allow or Never allow basis, and administrators can restrict this. By default, bots work on the account's cloud machine.
Can my colleagues message my Grok Bot?
As of September 2026 we found no feature for that. Bots can message each other and sit in group chats, and the enterprise edition lets an organisation give its members their own bots. Letting several people send work to one agent, with separate permissions for each, is what an agent room is for.
Does muti run when my laptop is closed?
The agent runs on your machine, so a sleeping machine is a sleeping agent. The daemon installs as a login service and resumes when the machine wakes. Requests sent in the meantime wait in the agent's inbox and run in order.
Sources
- Introducing Grok Bot: x.ai/news · more plans: x.ai/news · enterprise: x.ai/news
- Grok Bot docs, approvals, security and privacy: docs.x.ai · skills and routines: docs.x.ai
- InfoQ: infoq.com · Reworked: reworked.co
- Rakazo: github.com/elie222/rakazo
- The rest of the category: personal agents in 2026, compared
Cloud bots are the answer when the work has no home. When it already has one, on a laptop in your team, give it a room.
Veröffentlicht am