SPB Git

Repository Public

bots.md 5.3 KB 140 lines markdown

1<!-- source: https://docs.x.ai/grok-bot/bots (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Work with Grok Bot34# Create and manage Bots56A Bot is a durable AI teammate with a name, a job, its own conversation, and7working context that develops over time.89## Give each Bot a clear job1011Create a separate Bot when the work has a distinct:1213* Goal or area of ownership14* Set of tools and sources15* Working style16* Approval boundary17* Recurring schedule1819Good jobs include **Talent Scout**, **Expense Manager**, and **Bug20Reproduction**. A job such as **General Helper** gives the Bot less guidance and21makes its saved context harder to reuse.2223Describe the role in operational terms:2425> Own the weekly account-health review. Pull product usage and support signals,26> flag evidence of churn or expansion, and produce a linked watch list for the27> customer-success team. Never contact a customer or change an account without28> approval.2930## Create a Bot31321. Choose **New** in the sidebar or press `Cmd/Ctrl+N`.332. In **New chat**, select **Create new Bot**, or type a name and choose34   **Create “name” Bot**.353. Grok Bot creates and opens a Bot named **New Bot**.364. Open the Bot menu or choose **Edit Profile** to set its name, label,37   description, and avatar.385. Start a conversation with a concrete task.3940Your existing Bots can also suggest or create a focused Bot when a job should41have a long-lived owner. Ask before creating several Bots if you want to keep42the roster small.4344## Edit a Bot4546Open the Bot menu to change its name or description. Update the description47when you discover a durable preference, boundary, or responsibility that should48shape future work.4950Use the conversation for task-specific instructions. Use the description for51rules that should remain true:5253* **Description:** “Never send external messages without approval.”54* **Message:** “Draft follow-ups for these twelve accounts.”5556## Pin or hide a Bot5758* **Pin** active Bots to keep them at the top of the sidebar.59* **Hide from sidebar** removes a Bot from the main list without deleting its60  work.61* Open **Hidden Bots** at the bottom of the sidebar (when every Bot is hidden,62  the sidebar shows **Show Hidden Bots** instead), then choose **Unhide** to63  restore a hidden Bot.6465Hiding does not pause the Bot or its routines.6667## Duplicate a Bot6869Duplicate a Bot when you want the same role as a starting point for a different70scope—for example, one Account Health Bot per region.7172The copy is named "`<name>` copy" and carries the profile, settings, enabled73skills, routines, and avatar. It does not copy conversation history, learned74memory, or chat attachments. Rename it and provide the new scope before75assigning work.7677## Share a Bot7879Share a template when someone else should start from the same Bot.80811. Open the **Share menu** and choose **Create template**. The Bot builds82   the template; when it is ready, **Copy link**, **View template details**,83   and **Update template** appear.842. Choose who can open the link: **Public link** or **Team-only**. Accounts on85   an Enterprise plan default to **Team-only**; other accounts default to a86   public link.873. Send the link. The recipient opens a preview on88   [x.ai](https://x.ai) and can choose **Add to Grok Bot**. They need the Grok89   Bot app to finish adding it.9091A public link can be opened by anyone who has it and shows the Bot's shared92configuration, including its identity, description, skills, and routines; a93Team-only link opens only for members of your team. Remove API keys, internal94URLs, customer data, and anything else you would not put in a public document95before you share.9697Adding a shared Bot creates a copy on the recipient's account. It does not give98them your computer, logins, or conversation history.99100Shared Bots are created by other users, not by SpaceXAI. Adding one accepts the101[third-party bot terms](https://x.ai/legal/bot-sharing-terms).102103## Delete a Bot104105Deleting a Bot removes its active profile, conversation, and routines from Grok106Bot. Shared computer files and sign-ins are not isolated by Bot and may remain107on the computer. Backend retention follows the applicable Cursor terms.108109If you may need the work later, hide the Bot instead.110111## What a Bot remembers112113A Bot can retain stable working preferences, important facts, and summaries114from its work. This helps it keep a role over time without replaying every prior115message.116117Memory is not a substitute for an authoritative source:118119* Keep changing facts in the source system120* Ask the Bot to cite or reopen current data for consequential decisions121* Correct stale assumptions directly122* Put explicit safety boundaries in the Bot description123124Bots have separate roles and conversations, but they share the computer. They125can pass context through direct messages, group chats, and shared files.126127## Organize a team of Bots128129Start with the smallest useful roster:1301311. Give one Bot ownership of an end-to-end outcome.1322. Add another Bot only when the work has a stable specialist role.1333. Put Bots in a [group chat](/grok-bot/chat-and-collaboration) when the handoff itself134   needs to be visible.1354. Keep external actions behind a clear approval boundary.136137For example, a Website Launch group might include a launch coordinator, a138content editor, and an analytics reviewer. The coordinator can assign work,139while the group preserves the handoffs in one conversation.140
Files main
Menu

Theme