Create a new Grok Bot

Create a separate Bot when the work has a distinct goal, set of tools, working style, approval boundary, or recurring schedule. A named Bot keeps its own conversation and working context over time. Official guide: Work with Grok Bot → Create a Bot.

When a new Bot is the right move

Open a new Bot for jobs like Talent Scout, Expense Manager, or Bug Reproduction when you want guidance and reusable context for that role. Use a General Helper only when you do not need a durable job description. Prefer one Bot per clear owner and finish line rather than stacking unrelated work into a single conversation.

Create the Bot

1. Choose New in the sidebar, or press Cmd+N, then select Create new agent.
2. Click the Bot's name at the top of the chat, then choose Bot settings (or View conversation details → Bot settings / Agent settings).
3. Set the name, label, and description. Click the Bot's picture in the same panel to change its avatar.
4. Write the description in operational terms: what the Bot owns, which sources it should use, what finished work looks like, and what always needs your approval.
5. Send a real first task with a clear finish line. Prefer a task that spans a few tools and ends in a reviewable artifact.

Example description shape:

Own the weekly account-health review. Pull product usage and support signals, flag evidence of churn or expansion, and produce a linked watch list for the customer-success team. Never contact a customer or change an account without approval.

First task that teaches the role

Hand the Bot a concrete assignment rather than a tour of features. Name the sources, the deliverable, the deadline, and the approval boundary. After it returns, correct the result in the conversation, then put durable rules into the description so the next run starts from those rules.

Your existing Bots can also suggest or create a focused Bot when a job should have a long-lived owner. Accept that handoff when the new work would dilute the current Bot's job.

Pitfalls

• Leaving the description empty — the Bot has no durable job boundary until you write one.
• Mixing several unrelated roles into one Bot — create another Bot when the tools, schedule, or approval boundary diverge.
• Putting changing facts only in memory — keep authoritative numbers and lists in the source system and ask the Bot to re-read them for consequential decisions.
• Expecting a new Bot to start with a private computer — every Bot on your account shares the same cloud computer, files, and browser sessions.