“Grok agents” can mean three different things at xAI. For most people it means Grok Bot, which xAI calls “your team of always-on agents”: named Bots that do real work on their own cloud computer. Developers might instead mean the Grok API’s multi-agent model or the subagents in Grok Build, xAI’s coding agent. This page tells you which is which and how to build your first one.
The three kinds of “Grok agent”
| Grok Bot Bots | Grok API multi-agent | Grok Build subagents | |
|---|---|---|---|
| What it is | Always-on AI teammates with names, jobs and memory | A model where several agents research together and a leader agent writes the answer | Child sessions inside xAI’s coding agent |
| Who it’s for | Anyone. No code needed | Developers building apps | Developers working in a code repo |
| Where it runs | A persistent cloud computer with a browser, files and a terminal | xAI’s API (grok-4.20-multi-agent, in beta) | Your terminal, through the grok CLI |
| How you set it up | Message it in the Grok Bot app | API call, with 4 or 16 agents | Built-in types (general-purpose, explore, plan) or your own in .grok/agents/ |
| How you pay | Included with plans that include Grok Bot | Per token, plus tool calls | X Subscription (Plus and up list Grok Build) or an xAI API key |
If you landed here wanting an AI that does tasks for you, you want Grok Bot. The rest of this page focuses on that.
How a Grok Bot “agent” works
From xAI’s docs:
- Each Bot has a job. It has a name, its own conversation, and context that builds up over time. xAI suggests focused jobs like “Talent Scout” or “Expense Manager” over a vague “General Helper”.
- Each Bot has a computer. All your Bots share one persistent cloud computer, so work continues when your laptop is closed.
- Bots work together. They can run in parallel, message each other, share context in group chats and pass ownership of a task.
- Bots learn your workflows. You can show a Bot a task once and save it as a skill, then run it on a schedule as a routine.
Create your first Grok agent in 5 steps
- Get access and install the app from x.ai/bot. (Which plans include it: Grok Bot pricing.)
- Create a Bot: choose New chat → Create new Bot, or press Cmd/Ctrl+N.
- Give it its job in the first message, and ask it to remember:
Own the weekly competitor check. Each Monday, review these five competitors’ sites and posts, list anything new with links, and flag pricing changes. Never contact anyone. Remember this for future work.
- Give it a real first task with a clear finish line, then correct the result.
- Save and schedule it: “Save this as a skill called Competitor check,” then “Run it every Monday at 9 AM.” Test the routine with safe inputs first.
Our free lesson Grok Bot in 5 minutes walks through the basics.
What about “custom instructions”?
With Grok Bot, a Bot’s standing instructions are just what you tell it to remember. xAI’s docs separate two kinds of message:
- A lasting rule: “From now on, never send external messages without approval.”
- A one-off task: “Draft follow-ups for these twelve accounts.”
For longer, reusable instructions, save a skill. xAI’s docs say a good skill states when to use it, the inputs and access it needs, the steps, how to check the result, what to return and what needs approval.
Going multi-agent: the “swarm” pattern
xAI says people inside the company often run several Bots in parallel, with one managing the others: “a chief of staff sits on top, with a specialist for each lane.” A simple version:
- Chief of staff: keeps the to-do list and hands work out.
- Two or three specialists: inbox, research, content or code, each with its own job and approval rules.
- A group chat where they pass work, and only pull you in for judgment calls.
Start with one Bot. Add the next one when a job clearly needs its own tools, schedule or approval rules. Our free lesson Why split work across bots covers when it pays off.
Related bots from the library
- Chief of Staff: your coordinator Bot. It hands work to the right Bot and sends you one brief.
- Projects Manager: spins up a coder, designer, researcher and writer as separate Bots.
- Agent Manager: reviews your roster for overlaps and quiet desks.
- The Cleaner: an independent auditor for multi-bot teams.
- Overwatch: keeps a shared multi-bot workspace organized and backed up in git.
- Code Team Spawn: stays idle until you need a coding team.
Browse all Grok Bot templates.
Get the free setup guide
Our free 18-page setup guide shows you how to build your first agents and how to make them work as a team. Get the free guide
FAQ
What are Grok agents?
Usually Grok Bot’s Bots: always-on AI teammates that work on a cloud computer. For developers, it can also mean the Grok API’s multi-agent model or Grok Build’s subagents.
Do I need to code to build a Grok agent?
No, not with Grok Bot. You create a Bot and describe its job in plain language. The API and Grok Build options are for developers.
How many agents does the Grok API multi-agent model use?
You can choose 4 or 16 agents. xAI says 16 goes deeper but uses far more tokens. The model is in beta.
Can Grok agents work together?
Yes. Grok Bot’s Bots can message each other, share context in group chats and hand off tasks.
What’s a Grok agent builder?
Grok Bot doesn’t use a drag-and-drop builder. Setup is a conversation. Templates are a shortcut: add one from our library and adjust it.
Swarm School is an independent site. We’re not affiliated with xAI.
Sources
- https://x.ai/news/introducing-grok-bot
- https://docs.x.ai/grok-bot/overview
- https://docs.x.ai/grok-bot/bots
- https://docs.x.ai/grok-bot/chat-and-collaboration
- https://docs.x.ai/grok-bot/skills-routines-and-automations
- https://docs.x.ai/developers/model-capabilities/text/multi-agent
- https://docs.x.ai/build/overview
- https://docs.x.ai/build/features/subagents
- https://x.ai/pricing
Swarm School is independent and not affiliated with Grok Bot’s makers. Features change; check the official docs for current details.