Manage Grok Bot Bots: Create, Edit, Organize, Share and Delete

Create a separate Bot when the work has its own goal, set of tools, working style, approval boundary or recurring schedule. Cursor's docs describe a Bot as a durable teammate with a name, a job, its own conversation and context that builds up over time, and that last part is the reason to split roles. A Bot called Talent Scout or Bug Reproduction gets guidance from its job, and its saved context stays reusable for that job.

A General Helper gets neither benefit, according to the docs. Everything it learns is about everything, which makes it hard to predict what it will apply where.

Describe the role in operational terms. The docs' own example reads like a job description with a hard stop at the end: own the weekly account-health review, pull product usage and support signals, flag churn or expansion evidence, produce a linked watch list for customer success, and never contact a customer or change an account without approval. Your existing Bots can also suggest or create a focused Bot when a job should have a long-lived owner.

Creating the Bot takes seconds. The first message is where the setup actually happens, so plan it before you click.

1. 1Choose New Bot (the + button) in the sidebar, or press ⌘+N. On a team, + opens a menu; choose Create a Bot.
2. 2Name the Bot, pick a shape and color, and choose Create.
3. 3In the first message, give it its job, its sources and its approval boundaries, and ask it to remember them.
4. 4Send a real first task with a clear finish line.

Asking it to remember the job is the step people skip, and it matters because the Bot otherwise decides on its own what is worth keeping. The Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. memory guide explains what it keeps and how to check. For the first task itself, the docs' use cases page has starter prompts by role, and the use cases article walks through them.

Each Bot has its own name, picture and label, and only the Bot's owner can change them. There is no Bot settings page any more and personal Bots no longer have a description, so everything visual lives in the Bot's details: click the Bot's name at the top of the chat (View conversation details) to open them.

If Rename Bot is missing from the right-click menu, you do not own that Bot. If the sidebar is collapsed to icons, expand it first.

Changing what a Bot does happens in chat. Tell it, and for a lasting rule, ask it to remember, as in "From now on, ask before sending any email." Keep task instructions in ordinary messages, such as drafting follow-ups for twelve accounts. The distinction sounds fussy until a one-off instruction quietly becomes a standing rule, at which point it is the whole problem. A Team Bot is the one exception that still has a description, edited by its owner or a Manager under About; Team Bots covers the rest.

Sidebar sections group Bots by project, client or business, and Pin keeps active ones at the top. Sections sync between desktop and iOS, and deleting a section moves its Bots to Unassigned without deleting them.

• Desktop: right-click a Bot, choose Move to new section, or Move to and a section (or Create section) once you have one. Right-click a section name and choose Rename to label it.
• iOS: touch and hold a Bot, tap New Section, or Move to and pick a section. Sections need Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. v1.2.0 or later on iOS.
• Hide: right-click and choose Hide from sidebar. The Bot stays active, keeps its history and keeps running its routines, but sends no notifications.
• Unhide: open Hidden Bots, right-click, Show in sidebar on desktop; Show Hidden Bots then Unhide on the phone.
• Duplicate (iPhone): copies profile, settings, enabled skills, routines and avatar, but no conversation history, learned memory or attachments.

Duplicate is the move when you want the same role at a different scope, like one account-health Bot per region. Rename the copy and give it its new scope before assigning work, since it arrives with the routines but none of what the original learned.

A public link lets someone else start from the same Bot. It exposes the shared configuration (identity, description, skills and routines), so strip API keys, internal URLs and customer data before you share. The recipient adds a copy to their own account and never gets your computer, your logins or your conversation history. Adding a shared Bot also accepts the third-party bot terms shown at that point.

On the Teams and Enterprise plans, admins decide whether members can publish Bot templates publicly at all. If what you want is one Bot your whole team talks to, rather than a copy each, that is a Team Bot, which has its own page.

Messaging a Bot works like messaging a teammate. You can paste text, links and images, attach files, ask for a saved skill by name, mention a Bot, group, routine or app with @, reply or react, and send another instruction while work is running. A direct message from you takes priority over background work and can redirect the current turn. "Stop now" ends work immediately, though it does not undo actions the Bot already completed.

Tell the Bot what each attachment is and how to use it. Large, encrypted, damaged or unusual files may not be readable, and the docs suggest exporting those to PDF, CSV, plain text or an image.

Bots can also message each other asynchronously. The receiving Bot wakes, handles the request and can reply later, and you see the handoff in the conversation. Handoffs suit the case where one Bot owns a source system and another owns the deliverable. Ask for a single owner at each stage, because parallel handoffs create duplicate work and noisy updates. Group chats and the Slack rules for handoffs live in the group chats and voice guide.

For results you can trust, name the artifact and its acceptance criteria up front, then ask the Bot to separate facts found in sources, assumptions, completed actions, actions waiting for approval and open questions. Reply in a thread when feedback applies to one result, and ask the Bot to revise the existing file rather than make a disconnected copy.

The sidebar shows three states: needs attention (a question, approval or handoff), unread activity (a new result) and working. Opening a conversation marks it read, and the Bot menu can mark it read or unread by hand.

Turn on Notifications for a Bot to get an alert when it finishes or is waiting for you. On the phone the switch is in the Bot's profile; on desktop, you ask the Bot to turn its notifications on or off, which is a little odd the first time. Alerts are suppressed while Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. is the focused window, though the sidebar and dock badge still show activity. On iPhone, both the device permission and the Bot's setting must allow it, and push delivery is rolling out gradually.

Helper Bots, which your Bots create to help with their own work, show up in the sidebar and notify you like any other Bot. Ask a helper to turn its notifications off, or hide it.

Right-click the Bot in the sidebar and choose Delete. That removes its profile, conversation and routines, and the memory help page adds that it also erases the Bot's memory and attachments, including shared facts it saved for your other Bots. It cannot be undone.