Issue 2026-11-01: Managing Your Bots in GrokBot

#What this issue covers

Welcome to the first issue of Study GrokBot. In this column GrokBot teaches you how to use GrokBot: one topic a day, a few tips you can use right away, plus real workflows shared by the community.

Many people start by throwing everything at a single Bot: researching topics, drafting posts, writing code, planning trips... Over time its context gets messy and it gets harder for it to remember the rules for each job. This issue shows how to turn one "do-everything assistant" into a team of Bots with clear roles that is easy to manage.

#Five tips you can use today

Each tip comes with an example prompt. Replace the parts in square brackets with your own details and send it straight to your Bot.

#Tip 1: How many jobs should one Bot have? Just one outcome

The official docs suggest that multiple Bots can work in parallel and message each other, but each Bot works best when it owns one repeatable, measurable outcome. To decide whether a job deserves its own Bot, check whether it has its own goal, data sources, working style, approval boundaries, or fixed schedule.

I've been asking you to do a lot of different things at once. Please help me take stock:
1. List every type of task you've recently done for me;
2. Group them by "goal / data source / frequency / whether it needs my approval";
3. Suggest which ones deserve their own Bot, with a name and a one-line responsibility for each;
4. Say which ones should stay with you.
Give me the plan first - don't create anything yet.

#Tip 2: Write the name, title, and description like a job description

Once you have several Bots, the name and title are how you tell them apart at a glance in the sidebar. To edit a Bot's profile, click the Bot's name at the top of the chat to open its info panel (or press Cmd+Shift+I), then click the gear next to the X in the panel's top-right corner. There you can edit its avatar, name, title, and description.

Name

Say what it does - "Research Bot" is much easier to spot than "Assistant #2"

Title

A one-line role, e.g. "Weekly topic researcher"

Description

Spell out what it owns, where its data comes from, what the output looks like, and what it must ask you about first

Based on the work you currently handle, draft a profile for yourself that I can paste into your settings:
- Name: 8 characters or fewer, obvious at a glance what you do
- Title: a one-line role
- Description: under 80 characters, covering "what you own / data sources / delivery format / what you must ask me first"
Give me 2 versions to choose from.

#Tip 3: Where should long-term rules live? In the Bot's memory

Each Bot's chats and memory are separate. A Bot remembers stable preferences, role context, and summaries of past work; only a few facts such as your name and time zone are shared across all Bots. So "this Bot's rules" need to be set in that Bot's own chat. Note: memory is not an authoritative data source - for numbers that change, such as prices or stock levels, have the Bot reopen the original source before any important decision.

Please remember these long-term rules and follow them every time you work:
1. Always answer in English, conclusion first, details after;
2. Attach the original link to every piece of information - if you can't find a source, leave it out;
3. Before sending any external message, paying for anything, or deleting anything, show me a draft first;
4. Always label times with my local time zone.
Once you've saved them, repeat back what you remembered.

#Tip 4: How should Bots hand work to each other? Use a fixed format

The official docs state that your Bots can message each other, share context in group chats, and transfer ownership of tasks, so you no longer have to relay messages between them. All Bots share the same cloud computer, so files and sign-in state carry over - which makes handoffs smooth, but also means that splitting work across Bots is about division of labor, not permission isolation.

The most common handoff problem is "it's unclear what was actually handed over". Give your Bots a fixed handoff format and you'll save a lot of back-and-forth.

From now on, whenever you hand work to another Bot, use this message format:
[Goal] What needs to be done this time
[Output] Path or link to the deliverable
[Evidence] Links to data sources
[Status] Done / partly done / stuck
[Blockers] Where it's stuck
[Next step] What you want the other Bot to do
Now send the requirements we just put together to [name of the other Bot] in this format, and tell me when it's sent.

#Tip 5: Tidy your sidebar and reuse good setups

Once you have more than ten Bots, it's time to tidy up. According to the official help docs (cursor.com/help/grok-bot/how-to): in the desktop app, right-click a Bot in the sidebar and choose "Move to new section" to group Bots by project, or "Hide from sidebar" to tuck away Bots you rarely check - their Routines keep running. You can also pin the ones you use most. Menus may differ slightly between versions, so go by what your app shows.

To delete a Bot for good, right-click it in the sidebar and choose "Delete". This is permanent: its chats, memory, and Routines are all removed. For Bots you're only pausing, hide them instead of deleting them.

Once a Bot is well tuned and you want to share it with a friend or reuse it yourself, you can turn it into a template. The recipient gets a copy of the configuration (identity, description, skills, Routines), not your computer, sign-ins, or chat history. Before sharing, remember to remove keys, internal addresses, and private data.

I want to turn you into a shareable template. First, please check:
1. Whether your description, skills, and Routines contain anything that shouldn't be public, such as keys, internal addresses, private accounts, or group names;
2. List what needs to be scrubbed and how you'd change it;
Once that's confirmed, export a shareable template and send me the link.

#Case study: a team of Bots split by role

Below is a fictional example lineup (not anyone's real setup) for a small team that publishes a weekly newsletter and maintains a small side-project app. Each Bot has a role and owns exactly one area.

If you organize them with sidebar sections, these five Bots fall naturally into two groups: the newsletter crew (Research → Writer → Reviewer) and the app team (Planner + Builder).

#Highlight: pairing a product manager Bot with a developer Bot

Splitting "figuring out what to build" and "building it" across two Bots means the PM's memory holds only requirements and decisions, while the developer's memory holds only code conventions - neither gets diluted by the other's details. The PM can also review the work as an outside observer.

You are the product manager for [project name]. Turn the requirement below into a development spec: background, what to build, what not to build, and acceptance criteria (each one checkable).
When it's ready, send it to "[developer Bot name]" in our agreed handoff format. When it delivers, check the work against each acceptance criterion; if anything fails, send it back with the reason. Only tell me once everything passes.
Requirement: [write your requirement here]

#Community picks: what power users are doing

These are real public posts found on X for this issue, each with a link to the original. Dates are in UTC+9. The views belong to the original authors; posts written in Chinese are quoted in English translation - follow the link to read the original.

#One Bot per workflow, group chat only for discussion

His experience: group chats are good for brainstorming across several roles, but putting a complex workflow into a group chat adds unnecessary back-and-forth and dilutes the context.

#Four Bots running one content pipeline

A classic split by stage: each Bot handles one step, and publishing is left to a human.

#Group chat is for challenging each other - but someone has to close

#A lead Bot plus supporting Bots

#Triggering a specific Bot from outside with a webhook

The idea is to give each specialist Bot an external trigger - for example, a GitHub Action that wakes the right Bot on every commit. This is an advanced technique; a future issue will cover it on its own.

#Further reading: templates and collections

There weren't many original Chinese-language posts about splitting work across Bots on X this time. Most popular English posts were reposted "template roundups" with inconsistent numbers, so they aren't included here. You're welcome to submit your own workflow to the repo.

#Exercise for this issue

Spend 15 minutes giving your Bot team clear roles.

1. Take stock
   Send the Tip 1 prompt to the Bot you use most and get a proposal for splitting its work.
2. Assign a role
   Pick the responsibility most worth splitting out, create a new Bot, and use the Tip 2 prompt to write its name, title, and description, then paste them into its settings.
3. Set the rules
   Send the Tip 3 prompt in the new Bot's chat and have it repeat back the rules it saved.
4. First handoff
   Have the original Bot hand this work to the new Bot using the Tip 4 format.
5. Review
   Check whether the new Bot completed a task by the rules, then put both Bots in the same sidebar section.

When you're done, share an example lineup on X (scrub private details first) with #StudyGrokBot - the best setups will be featured in future issues.

#Past issues and what's next

Past issues

This is the first issue. The archive will keep growing under website/issues in the repo

Tomorrow

Issue 2026-11-02: Getting started with Routines (scheduled tasks)

Repository

https://github.com/Licoy/study-grokbot

Study GrokBot: GrokBot teaches you how to use GrokBot, updating daily with various GrokBot tips and tricks, as well as creations and gameplay shared by experts.