You're one app install away from a team that takes on your biggest jobs.

The bar I’m using now is simple. Did my agent tell me what to do, or did it hand me the finished thing?

Told is last year. Done is the frontier.

Most AI still runs on told. It reads your inbox and gives you a summary. It scans your calendar and gives you a briefing. It builds a dashboard nobody opens. You still do the work.

My mom uses email for email and the browser for the internet. That’s it. Until now she had no way to even understand agents, let alone use one. Grok Bot crosses that chasm. She can install one app, name a Bot, tell it what she wants, and watch the little guy open its own computer and start working. When a login appears, she takes the mouse, signs in herself, and hands control back. No agent framework, no terminal, no Mac mini on a shelf.

I have spent years building AI teams in terminals, folders, agent harnesses, and project systems. The power has been real for a long time. Getting to it meant choosing a framework, connecting services, managing credentials, and enjoying the machinery enough to keep the whole thing alive. Grok Bot is the first time I opened a consumer app and felt the whole multi-agent idea arrive at once.

In roughly eight hours, I built twelve working Bots. One became my Chief of Staff, another led a landing-page project, and a research specialist looked for customer language. Other Bots worked through Gmail, Slack, Google Calendar, and LinkedIn. Others took travel planning, exercise, and contact research. One went looking for a backyard sauna that could get hot enough. By the time I sat down to write this piece and record my video, I had already gone past twelve because every project in my life started suggesting another useful role.

Every Bot had a name, a continuing job, a conversation, and its own screen. All of them shared one cloud computer assigned to my account: the files, the browser sessions, the connected tools, the command-line credentials.

That shared computer is the point.

It’s why one Bot can research something, save it, and message another without making me download the file, upload it somewhere else, and restate the assignment. I stopped being the integration layer between two AI chats.

Grok Bot turns those parts into concepts people already understand: a teammate, a job, a conversation, a computer, a file, a message, and a moment when the person needs to take over. The technical system is still underneath, but the person gets to work at the level of the thing they want to make.

Grok Bot is the multi-agent product for knowledge work, and it’s finally here.

The two Bots you’ll get are both built on done. One goes looking for work already sitting in your sources and prepares the finished version. The other takes a business idea and builds the motions around it. Something exists at the end that didn’t exist before, and you didn’t have to make it.

Here’s what’s inside:

• The shared computer. Why one Linux box behind twelve Bots is the decision that makes the whole thing work, and why it’s also the security boundary.

• What twelve Bots taught me. The rule that stops you from building a dozen useless roles: a Bot owns a theme, not a task.

• The $200 question. The real price range, and the value bar I’d set before you spend anything.

• Two Bots to start with. Grab the Super Doer Bot and the Business in a Box Bot, both built to leave finished work behind instead of another briefing.