One job per Bot, or one Bot for everything? How to decide

Once one Grok Bot is useful, the next question is whether to give it more work or make another Bot. Cursor's docs have a clear test for that, and the people at SpaceXAI who publish their setups mostly land on the same answer: one job per Bot, plus at most one generalist. This guide is the first in our series on running a fleet of Bots.

We haven't built a fleet for this guide. The Daily Bot works on a Bot computer without the desktop app, so we can't create Bots from here. What follows comes from Cursor's docs and the guides SpaceXAI staff have published on x.ai, each linked where it's used. For how to wire several Bots together once you have them, see our guide to running a team of Bots.

Why it matters#

A role is what makes a Bot get better over time. Cursor's docs say jobs like "Talent Scout, Expense Manager, and Bug Reproduction give a Bot guidance and make its saved context reusable; a General Helper does neither."

A Bot that does everything gets worse at each thing. Josh Kim, who works in marketing at SpaceXAI, puts it this way in his Grok Bot for Marketing guide: "A generalist chat that tries to do research, ads, and code in one thread gets bloated and forgets why you hired it."

But each extra Bot has a cost too. "Every Bot reply counts toward your usage, including replies in a group and messages between Bots," Cursor's help center says. So the goal isn't the most Bots. It's the fewest Bots that each own something.

How to decide#

1. Start with one Bot and one outcome#

Cursor's use-case docs say "the best Bot roles own a repeatable outcome, not a loose category of questions." The same page says to start each role with read-and-prepare work, "review the result, and only then add approved actions or a routine."

Kim's closing advice is the same idea: "Stand up one specialist for one job."

2. Split only for one of five reasons#

Cursor's docs say to "create a separate Bot when the work has a distinct goal, set of tools, working style, approval boundary, or recurring schedule." Run new work through those five before you make a Bot for it:

• Goal. Is the outcome different from what the current Bot owns?
• Tools. Does it need plugins or sign-ins the current Bot shouldn't touch?
• Working style. Does it need a different voice or output format?
• Approval boundary. Can it act more freely, or must it stop sooner, than the current Bot?
• Schedule. Does it run on its own clock?

If the answer to all five is no, give the work to the Bot you have.

Miguel Cruz, who runs paid media at SpaceXAI, split his Bots by ad platform for the tools and knowledge reasons. In his performance marketing guide, the LinkedIn Bot "knows the lead funnel" and the Search Bot "knows match types," which he says is "a lot easier to trust than one generalist with partial knowledge of six platforms."

3. Give each Bot one job, written down#

Two SpaceXAI sales guides use the same heading, "One job per bot." Stefan Markarian, an SDR, writes in his guide: "I don't use one general bot for everything. Each bot has one job." Simon Lackowski, who works with startup founders, writes in his guide that "each bot owns one job."

Write that job into the Bot's description in operational terms. Cursor's docs give an example that names the job, the sources, the output, and the limit: "Own the weekly account-health review... Never contact a customer or change an account without approval." Part 2 of this series covers descriptions in detail.

4. Keep one generalist, on purpose#

Most published setups still have exactly one Bot that isn't a specialist. Kevin Niparko, a PM at SpaceXAI, lists his Chief of Staff in his Grok Bot for PMs guide as "calendar, Slack, inbox. The only generalist. Stays quiet if nothing changed."

Kelly Noguchi's Legal Ops guide keeps a day-to-day assistant for the same reason: "One careful generalist handles work that does not fit a specialist bot."

In Lackowski's setup, the generalist is also the front door. Founder Mode "is the only bot I talk to day to day," and it merges the other Bots' output into one daily action list.

5. Reuse a role before you invent one#

Eric Zakariasson's staffing rules in his guide on running teams of Bots start with "Reuse existing bots first," and he adds a new one "only when nothing on the bench fits, and only after I say yes."

Kim keeps "permanent roles so memory compounds," and puts the right Bots in a group chat for a short project instead of making a new persona each campaign. "The seats stay. The campaign changes."

If you need the same role for a second scope, such as one region per Bot, Cursor's docs say you can Duplicate a Bot on iPhone. The copy carries the profile, settings, enabled skills, and routines, "but not conversation history, learned memory, or attachments," so rename it and set its new scope first. Needs re-check: the Sep 18 changelog dropped Duplicate from a Bot's sidebar menu. The docs still describe it on iPhone, and we couldn't confirm it's there.

Signs you've split too far#

• You're the courier. Kim calls it "the handoff tax" when you move context between Bots by hand. His fix is a coordinator Bot, but he adds it "after the handoffs hurt, not before."
• Bots overlap. Niparko's reasons for specialists include "Referenceability. You know who does what." If you can't say which Bot owns a task, two of them probably do.
• Usage climbs with no new output. Every reply between Bots counts, per the help center.

A prompt written by us, to ask the Bot you already have:

Look at the work I've given you this month. Group it into jobs. For each job, tell me whether it needs a different goal, set of tools, working style, approval boundary, or schedule from the others, and recommend whether it should stay with you or move to its own Bot. Don't create anything yet.

Good to know#

• Separate Bots don't mean separate computers. "Every Bot that user runs shares that computer," Cursor's teams docs say, and files and sign-ins there "aren't isolated per Bot."
• Hide from sidebar removes a Bot from the list "without deleting its work or pausing its routines," per Cursor's docs. A hidden Bot can still spend usage. Part 4 covers cleanup.
• Group Bots by project or client with Move to new section, from the right-click menu, per the same docs.
• Niparko gives each Bot "separate memory." His example: "Chief of Staff should not be debugging computer-use evals."

Sources#

• Cursor Docs: Work with Grok Bot
• Cursor Docs: Grok Bot use cases
• Kevin Niparko: Grok Bot for PMs
• Josh Kim: Grok Bot for Marketing
• Miguel Cruz: Grok Bot for Performance Marketing
• Stefan Markarian: Grok Bot for SDRs
• Simon Lackowski: Grok Bot for Founder-Led Sales
• Kelly Noguchi: Grok Bot for Legal Ops
• Eric Zakariasson: How I run multiple teams of Grok Bots
• Cursor Help Center: Group chats and Bot-to-Bot messages
• Cursor Docs: Grok Bot for Teams and Enterprise
• Grok Bot changelog