How to create a Grok Bot

Short answer: Creating a Bot means writing a name, one primary job and a description on your own account, then handing it a task with a clear boundary. The first time you open the app, you can pick a suggested teammate or create your own. Later, you start from New in the sidebar. That is not the same step as adding a template. A template is a recipe someone else packaged, and adding it gives you a copy. When you create from scratch, you write the name and the job. (get started, Bots docs, x.ai template guide)

Before you start

Get started lists three requirements. First, an eligible plan: every paid individual Cursor plan or the Cursor Teams plan, or an individual SuperGrok, SuperGrok Plus or SuperGrok Heavy subscription linked to your Cursor account. Current terms are on the Cursor plans page. This article does not list prices. Second, the Grok Bot desktop app for macOS, Windows or Linux. Third, an app or website where the first Bot can do useful work. You can also set up and use Grok Bot on a phone. (get started)

Grok Bot requires cloud data storage. If the account still uses Legacy Privacy Mode, move to a supported Cursor data setting before a Bot can start. (get started)

Sign in with a Cursor account. Choose Sign in on the welcome screen. If you are already in the app, choose Sign In with Cursor from Settings, finish in the browser, and return. If the organization requires single sign-on, use that flow. If access comes from SuperGrok, link it when the app asks. (get started)

On first use, the app introduces Bots, the shared computer and routines, then asks which tools you use. Those answers shape the first teammate suggestions. The docs say they do not connect or modify those tools by themselves. Computer setup runs in the background, and the last step opens Meet a future teammate. (get started)

From an empty start to a named Bot

1. Pick a suggestion or create your own. On Meet a future teammate, choose a suggested teammate or choose Create your own. Creating your own means a short name, one primary job, and a description of how it should work. (get started)
2. Later, create from the sidebar. Choose New, or press Cmd/Ctrl+N. In New chat, select Create new Bot. You can also type a name and choose Create “name” Bot. Grok Bot creates and opens a Bot named New Bot. (Bots docs)
3. Set the name, label, description and avatar. Open the Bot menu or choose Edit Profile. Keep the name short. The description should say how this one job works, and what it must never do. (Bots docs, get started)
4. Open with a concrete task. Start a conversation with a specific task. The docs say the Bot gets to work from that. Name the outcome, the sources, the limits, what it should return, and where it should stop for you. (Bots docs, get started)
5. Review before you make it repeat. Ask for a revision when something is missing or badly formatted, and name any preference that should last. When the process is stable, save it as a skill or create a routine. (get started, skills and routines)

Get started gives one filled-in example. The name is Piper and the job is product performance: investigate product-performance questions with observability tools, preserve links and screenshots, separate evidence from hypotheses, return a short summary with the highest-impact issue first, and never change production settings. You do not have to copy that job. The shape is the same: one job, how to do it, and one standing ban. (get started)

The Bots docs explain why not to write “do everything.” Split the work when the goal, the tools and sources, the working style, the approval boundary or the recurring schedule are different. Jobs they treat as sound include talent scouting, expense management and bug reproduction. A general helper gives less guidance, and saved context is harder to reuse. Write the description as an operational sentence, such as owning the weekly account-health review, and state that the Bot never contacts a customer or changes an account without approval. (Bots docs)

Description and message do different jobs. The description holds rules that should remain true, such as never sending an external message without approval. The message holds this task, such as drafting follow-ups for twelve accounts. When a new lasting preference, boundary or responsibility shows up, edit the description from the Bot menu. (Bots docs)

A Bot you already have can suggest or create a focused Bot when a job should have a long-lived owner. If you want the roster to stay small, ask it to check with you before it creates several. (Bots docs)

The phone entry is different. The mobile docs say the plus control on the home screen can choose New Bot or New Group Chat. On the phone you can also edit a Bot profile, manage group members, pin or hide a conversation, and delete a Bot. Some advanced desktop controls are not available on mobile. (mobile docs)

The official definition of the word Bot is in the glossary.

What to hand it first

Type, or dictate. On desktop, Start voice input is Cmd/Ctrl+D. On iPhone and Android, use Start dictation. Start voice chat is a live conversation. (get started, official FAQ)

Get started splits a strong request into five parts. Outcome: what finished looks like. Sources: which apps, websites, files or conversations count. Constraints: what the Bot must avoid or ask about first. Deliverable: what it should return. Review point: where it should stop for you. Missing those, the turn drifts toward chat. (get started)

For a result in about five minutes, with no connector and no website login, the docs say to attach a document. Ask for five bullets, a separate section of every date, decision and open question, a page or section citation for each item, and no change to the source file. That is a read-only preparation. It shows whether the Bot returns the format you asked for. (get started)

The next step is one of your own tools. The documented example opens an analytics dashboard, compares this week’s new-user activation with the previous four weeks, names the largest step-level change, and drafts a short investigation plan with links to the charts. It does not change dashboards, and it asks you to sign in if needed. Before you allow external changes, read the approvals and privacy page. (get started, approvals and privacy)

The use-cases page states the same order as how a role should start: read and prepare, review the result, then add an approved action or a routine. The expense example returns a summary and drafts, and does not send messages or change reimbursements. The product-performance example returns a short write-up with links, separates facts from hypotheses, and does not change alerts or production settings. Bug reproduction uses a fresh test account in staging, not production customer data. Provide test credentials through a secure handoff, not in chat. (use cases)

When a tool needs a sign-in, the Bot may ask you to take over the computer. Choose Take over in the conversation, enter the password, passkey, two-factor code or CAPTCHA yourself, then choose I'm done to hand control back. The browser session persists on the shared cloud computer, so other Bots can use that signed-in session when it is appropriate. For a supported service, you can also install a plugin from Connect apps in the sidebar and authenticate in the browser. (get started)

When you review the result, ask for a revision if it is incomplete or formatted wrong, and name the lasting preference out loud. The documented example is a future weekly-report format: five bullets, source links inline, and a final section called Decisions needed. Save a skill or create a routine only after the process is stable, not on the first turn. (get started)

Sending, purchasing, deleting, publishing or changing a production system should sit behind approval. Put standing boundaries in each Bot’s description, and add narrow Ask first rules for those actions. Passwords, two-factor codes and CAPTCHAs use a takeover, not a paste into ordinary chat. The template safety checklist collects those rules. (official FAQ)

How this differs from adding a template

The template guide calls a template a recipe, not a meal. It packages instructions, relevant memories, skills and some plugins so someone else can get a Bot in their own app, or so you can use a Bot someone else built. They do not receive a one-to-one clone. Custom code and scripts are not included. (x.ai template guide)

The Bots docs describe the receiving side. Adding a shared Bot creates a copy on the recipient’s account. It does not hand over your computer, logins or conversation history. A public link shows identity, description, skills and routines. Shared Bots are created by other users, not by SpaceXSI. Adding one accepts the third-party Bot terms. (Bots docs)

The two paths start in different places. Creating from scratch means you write the name and the job in Edit Profile or at creation time, and the conversation starts from the first task you give. Adding a template means accepting a recipe that is already written and generating a copy on your account. Plugins on that copy usually need you to reconnect them. The clicks are in how to add a template. When your own Bot is worth someone else’s starting point, read how to make and share a template.

Marketplace in the sidebar is a third door, and it is still a template, not a blank Bot. Choose Add on a Bot, or open it and choose Import Bot, to create your own copy from its template. (Bots docs)

If you want to see what other people have shared for hiring, the Recruiting & job search collection on this site filters by the public summary. It is not an official job list. Which one fits still depends on the template’s own description and the tools it asks to connect.

What you can do after it exists

Pin a Bot you use often so it stays at the top of the sidebar. Hide from sidebar only removes it from the main list. It does not delete the work, and it does not pause the Bot or its routines. Hidden Bots at the bottom of the sidebar can show it again. On iPhone and Android, choose Unhide in the hidden list. If you may need the work later, the docs say to hide rather than delete. (Bots docs)

Deleting removes the Bot’s active profile, conversation and routines from Grok Bot. Because Bots share a computer, files and sign-ins on that computer may remain. Backend retention follows the applicable Cursor terms. (Bots docs, official FAQ)

Duplicate when you want the same role for a different scope, such as one account-health Bot per region. The copy is named with “copy” after the original name. It carries the profile, settings, enabled skills, routines and avatar. It does not copy conversation history, learned memory or chat attachments. Rename it and write the new scope before you assign work. Sharing a template, not duplicating, is how someone else gets a starting point. (Bots docs)

Keep the roster small. The documented order is: give one Bot an end-to-end outcome; add another only when a specialist role is stable; put Bots in a group chat when the handoff itself should stay visible; keep external actions behind a clear approval boundary. A website-launch example can include a coordinator, a content editor and an analytics reviewer. The coordinator assigns work, and the group keeps the handoffs in one conversation. (Bots docs)

FAQ

On first open, do I write a Bot or pick a suggestion?

Either. Get started says to choose a suggested teammate on Meet a future teammate, or choose Create your own and give a short name, one primary job and a description of how it should work. Suggestions come from the tools you said you use. Those answers do not connect the tools.

Is creating a Bot the same result as adding a template?

No. Creating means you write the name and the job on your account. Adding a template generates a copy from someone else’s recipe. The docs say that copy does not include their computer, logins or conversation history. Plugins on the copy usually need to be reinstalled by you.

Should the first task send messages for me?

The documented starting order is read-and-prepare work, then a review, then actions that need approval. The first example in get started summarizes an attachment and does not change the source file. For sending, purchasing, deleting, publishing and production changes, the FAQ recommends narrow Ask first rules and standing limits in the description.

Based on get started and Bots (Oct 12, 2026), the official FAQ (Sep 29, 2026), use cases, mobile, approvals and privacy, skills and routines, the x.ai template guide (Sep 8, 2026) and the Cursor plans page. Last checked: 2026-10-18. Bests.one is not affiliated with xAI.