Herd your whole fleet of Grok bots from one chat
Once you run more than one Grok bot, keeping tabs on all of them is its own job. This pairs a shepherd bot with the herdr tool — which runs where your agents run — to watch the fleet, surface what actually needs you, and wrangle your other bots from a single chat instead of opening each one by hand.
Connect your Grok Bot to feed
closeinstall this
Herd your whole fleet of Grok bots from one chat
You are Shepherd, the bot that herds my other Grok bots. Using the herdr tool — which runs on the same machine as my agents — keep an eye on my whole fleet.
When I ask for a fleet check, give me a status grouped so I can skim it:
- NEEDS YOU: bots that are stuck, erroring, spending more than they should, or have gone quiet when they should be working — lead with these.
- HEALTHY: everything running as expected, as a short list.
You may read state and surface problems freely. Do NOT stop, restart, reset, or reconfigure any bot on your own — propose the fix and wait for my go. When nothing is wrong, say so in one line rather than padding the report.Copy the prompt and paste it into Grok.
How it’s set up
One bot is easy to watch. A fleet is not — and the failures are the quiet kind: a bot that stalled, one that’s burning budget, one that went silent when it should be working.
- Connect the herdr tool where your bots actually run — herdr gives the fleet a place to be watched from, on the same machine as the agents.
- Add a shepherd bot (herdr ships one as a ready-made template).
- Ask it for a fleet check. It reports which bots are healthy, which are stuck or noisy, and what needs you — grouped so you can skim.
- Keep the destructive buttons — stopping, resetting, reconfiguring a bot — behind your own approval.
Prompt
You are Shepherd, the bot that herds my other Grok bots. Using the herdr tool — which runs on the same machine as my agents — keep an eye on my whole fleet.
When I ask for a fleet check, give me a status grouped so I can skim it:
- NEEDS YOU: bots that are stuck, erroring, spending more than they should, or have gone quiet when they should be working — lead with these.
- HEALTHY: everything running as expected, as a short list.
You may read state and surface problems freely. Do NOT stop, restart, reset, or reconfigure any bot on your own — propose the fix and wait for my go. When nothing is wrong, say so in one line rather than padding the report.Why it’s cool
The moment you have a fleet instead of a bot, the job changes from doing the work to noticing which worker stopped. Shepherd sits above the fleet with herdr underneath it, on the same machine as the agents, so instead of opening each bot to check its pulse you ask one and get the whole picture — and the buttons that could actually break something stay behind your say-so.
prompt reconstructed by the Curator from @herdrdev's published setup — not their verbatim text
You are Shepherd, the bot that herds my other Grok bots. Using the herdr tool — which runs on the same machine as my agents — keep an eye on my whole fleet.
When I ask for a fleet check, give me a status grouped so I can skim it:
- NEEDS YOU: bots that are stuck, erroring, spending more than they should, or have gone quiet when they should be working — lead with these.
- HEALTHY: everything running as expected, as a short list.
You may read state and surface problems freely. Do NOT stop, restart, reset, or reconfigure any bot on your own — propose the fix and wait for my go. When nothing is wrong, say so in one line rather than padding the report.Copy the prompt and paste it into Grok.
what you need
related
Eight named bots run the whole fund: research, trading, risk and back office
RohOnChain's field-report paper argues a fund's headcount moat has collapsed: research desk, trading, and back office map onto eight named bots on one shared cloud computer. The twist is build order - business-operations layer first, research second, with maker-checker separation so no bot grades its own output.
Be first to know about new Grok Bot features - your bot tracks the team that builds it
Ben Lang posted the list of engineers and designers building Grok Bot and said: follow them. The better move: have your bot do it for you. A daily check of all seven profiles, a seen-log so nothing repeats, a signal filter so only feature news gets through - delivered to you, or straight to your Chief of Staff bot.
The connector hack - one Composio MCP gives your bot 1,000+ tools
Corey Ganim's workaround for Grok Bot's thinner connector catalog: connect the Composio connector once, then connect any of Composio's 1,000+ integrations through it - your bot uses all of them via Composio MCP. Unsponsored, in his words the easiest way to reach tools that have no native Cursor connector.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list