How to build a team of AI coworkers with Grok Bot (without touching code)

Most AI agent tools ask you to draw a node graph, write a system prompt in JSON, or open a terminal. Grok Bot asks you to open a chat window and click "plus." That's it. No wiring diagram, no framework, no yield curve of documentation to climb before you get your first task done.

That simplicity is the whole pitch. Instead of one assistant trying to do everything, you hire a small roster of named bots — a research bot, an inbox bot, a reporting bot — and each one runs on its own cloud computer with a browser, a file system, and a terminal attached to it. Each bot created inside Grok Bot gets its own virtual machine, described as a dedicated computer with a browser, file system, and terminal, letting a bot perform tasks independently, like browsing the web or managing files, separate from the main chat interface. You're not prompting a model. You're delegating to a coworker who happens to live in the cloud.

What exactly is Grok Bot?

Start at the source: x.ai/bot is where the product lives, and docs.x.ai is where the technical details are documented. Grok Bot is an always-on, multi-agent AI platform developed by xAI that operates as a team of specialized, named AI coworkers rather than a single general-purpose chat window. That distinction matters. A regular chatbot answers when you ask. Grok Bot keeps working in the background and only pings you when it needs a decision.

It's a team of always-on AI agents, each one running on its own cloud computer instead of your laptop, that can sign in to the tools you already use and finish multi-step jobs without you supervising every step — checking back in only when it needs a decision from you, and handing off work between multiple bots working together on the same task. Under the hood, three concepts drive everything: skills refer to the instructions used to complete a particular task, routines are the events or schedules that trigger the bot to start working, and plugins refer to the approved connections to applications such as Slack, GitHub, and users' emails. Get those three things right, and the bot runs itself. Get them wrong, and you end up babysitting a very expensive chat window.

How much does Grok Bot actually cost?

The pricing story here is genuinely confusing, and it's worth untangling before you sign up for anything. There's no dedicated "Grok Bot" subscription tier you buy on its own. xAI has not published a standalone price for Grok Bot — what you pay is the price of the subscription that carries it, either SuperGrok Heavy through xAI or Cursor Ultra or Cursor Teams Premium through Cursor.

At launch on August 11, access was locked behind the priciest tier available. Grok Bot isn't sold separately — to access it, you need an active Cursor Ultra subscription at $200 a month. That changed fast. Within about two weeks, xAI widened the door considerably. Users' own explanations pointed to heavy usage patterns straining the system, and xAI acknowledged the complaint on August 24 and reset everyone's weekly limits on August 26. The bigger shift, though, was on eligibility: every plan that includes Grok Bot after the August 26 expansion starts from 20 dollars a month, with a weekly usage meter and on-demand billing.

Check the SuperGrok pricing page directly before committing, since plan names and inclusions shift as the beta matures. Grok Bot access, connectors, higher rate limits, and SOC 2 compliance sit inside the Expert tier, with image and video generation and an upgrade path to SuperGrok at $100/month for higher usage. The takeaway: don't trust any single price you see quoted online, including this one. Read the plan page the day you subscribe.

How do you set up your first bot?

Getting started doesn't require any technical setup on your end. The installation process is as simple as can be — there is no need for any configurations or commands, and to start using the program, all you need to do is locate it in your application store or download it from the x platform.

Once you're in:

Log in with the account that holds your paid subscription. You should login using the account with the paid subscription, because if you need to change the account later, you'll need to build your agents from scratch.
Confirm your plan is eligible. Verify the plan and switch to the Grok Bot version if you're eligible for it — SuperGrok customers can continue using it directly.
Create your first bot. Give the agent a name, choose its color, form, and type, and set a description. Treat this like writing a one-line job description for a new hire, not a giant system prompt.
Connect its plugins. You then follow the steps to connect the bot to the plugins it needs to actually do the work — Gmail, Google Calendar, Slack, whatever the job requires.

That last step is where Grok Bot separates itself from a normal chatbot. Every plugin connection shows up visually, with its permissions listed on the bot's own page, so you can see exactly what each coworker is allowed to touch before it touches anything.

What can plugins and skills actually do?

Skills and plugins are the two building blocks that make a bot useful instead of just chatty. The official plugin documentation breaks down the distinction clearly: Grok discovers skills from project folders, user folders, any enabled plugin's skills directory, and extra configured paths, and user-invocable skills also appear as slash commands.

A plugin is bigger than a single skill. A skill is one SKILL.md file with one task focus, while a plugin can bundle skills, slash commands, subagents, MCP servers, and hooks under a single install. In practice, that means installing one plugin can hand your bot several new abilities at once instead of one narrow trick.

Once installed, you don't have to remember exact syntax to use them. Most plugins activate implicitly when your prompt matches a skill's trigger, but you can also call a plugin explicitly with @plugin-name or run its slash commands. For anything without a ready-made plugin, the bot doesn't just give up — it logs in through its own browser on its dedicated cloud computer, the same way a human assistant would open a tab and sign in manually.

What are good starter bots to build?

A few roles translate especially well into this format, because they're repetitive, rule-based, and don't require judgment calls on every run:

A research bot that runs a scheduled routine every morning, pulling news or competitor updates and dropping a summary in your inbox before you're even awake.
An inbox bot trained on your actual triage habits — which emails get archived, which get flagged, which get a canned reply.
A reporting bot that assembles a recurring document, like a weekly status report, using the same job description every time with only the data changed.

That reporting pattern is worth calling out specifically because it shows how fast bot-building gets once you have one working. Instead of writing a new job description from scratch, you copy the working one, paste it into a new bot, and edit two lines. A well-scoped bot's entire job can be a single sentence — check in every Friday, pull the numbers, format the report, send it.

What's the one rule you should never break?

Every plugin card shows its permissions printed right on it, which is genuinely useful for auditing what a bot can access. But that visibility only protects you if you also follow the one non-negotiable rule of working with any agent that can browse and log in on your behalf: never type a password, an API key, or a client's private data directly into a bot chat. Use the login flow. Use the plugin connection. Let the bot authenticate through the proper channel instead of pasting credentials into a text box that an AI model is reading.

This isn't specific to Grok Bot — it applies to every computer-use agent category, including tools like Cursor and other browser-automation agents. A bot capable of signing into websites, handling credentials, modifying files and executing terminal commands can make consequential mistakes or encounter prompt injection and malicious web content, which is why access to a user's local computer is treated as a separate permission from the cloud machine, making configuration and human review essential.

Is it worth setting up right now?

The honest answer is: it depends on how much repetitive, rule-based work already eats your week. If you're triaging the same kinds of emails, running the same research pull, or assembling the same report every Friday, a bot built once will keep paying that time back indefinitely. If your work is mostly judgment calls and creative decisions, you'll get less mileage out of delegation and more out of using Grok as a regular chat assistant.

Either way, the barrier to trying it has never been lower. Fifteen days ago this required a $200/month coding subscription. Now it starts at $20. Open the app, click plus, write one sentence describing the job, and see what your first coworker can actually finish before lunch.