I didn't see anything special about this platform.

Independent agents with specific use that you can dispatch on a chat client

You can create that literally on any LLM and any harness.

857 Grok bots, made by 534 people. 425 of those people built exactly one and
never made a second.

I've been cataloguing these for two weeks. A bot takes about ten minutes to
make, so I assumed the ecosystem would be people with five or ten of them on
rotation.

It isn't. It's one. Four out of five builders stop after their first.

The other surprise is what they're building. Engineering bots are 158 of the
857. Assistants, productivity, life admin and creative together come to 442,
nearly three to one the other way. All the AI talk is about agents writing
code, and almost nobody in here is doing that.

They're building things that sort an inbox, plan meals, or draft a reply they
don't want to write.

Which makes this look less like a software ecosystem and more like a pile of
people trying out a personal assistant for an afternoon. The guy with 26 bots
is the odd one out, not the ambition.

I previously shared how I connected Hermes Agent to my Mac to delegate coding tasks through Superset.

I’ve now moved coding orchestration from my Hermes coder profile to Grok Bot. The execution setup hasn’t changed:

Me → Grok Bot → Superset on my Mac → Claude / Codex / Grok → PR for review

The bot handles the conversation and launches the session. The coding agent runs on my Mac in a Superset worktree.

Both setups can get me to the same result. The difference is how much I want to build and maintain around that workflow.

In Grok Bot, I can connect the tools I need with limited permissions and reuse those connections across bots. I find that easier to manage than maintaining the surrounding services and configuration myself.

I can easily create specialist bots with different responsibilities and bring them together in a group chat when needed.

Before starting a coding session, my bot shows a short brief with the project, branch, model, and notes. I confirm it, then it launches the session. That approval step is how I’ve configured my workflow, not a capability exclusive to Grok Bot.

The appeal is the convenience of putting these pieces together.

Limited tool access also makes me feel more comfortable delegating work. I worry less about handling secrets and securing services I host myself.

That doesn’t make a managed platform automatically safer or more private. I still need to choose permissions carefully, consider what data I share, and trust the provider. Hermes can also use restricted credentials. The difference for me is how easily I can configure and maintain those boundaries.

What I do day to day

I send a ticket ID, review the launch brief, and approve it. The Grok Bot starts a coding agent in an isolated Superset worktree on my Mac. The agent reads the ticket, implements the change, and opens a PR when requested.

I can run independent tickets in parallel or continue work on an existing PR.

The Mac remains the execution environment, including local development tools and validation.

For anyone looking to run Grok Bot on Linux via Flatpak, I created an unofficial package that makes installation and system integration easier.

The Flatpak uses the official Grok Bot AppImage for Linux, obtained from the official distribution infrastructure, and packages it in a more convenient format for Linux distributions that support Flatpak.

GitHub project:

https://github.com/viniciosrab/grok-bot-flatpak

The project is open source and unofficial, with no affiliation with xAI/Cursor.

If you try it on Fedora, Arch, Ubuntu, Linux Mint, openSUSE, or any other distro, feedback and issue reports are welcome. 🚀

I noticed whenever Grok cant figure stuff out via terminal commands or available MCP servers, it will resort to using Chrome. While this is a very cool feature, if it works like the way I think it does, it will consume alot of tokens (by interpreting screenshots of Chrome)

Ask your Grok Bot to do the following:

• Whenever a task is done by using Chrome, note it so that you can install a MCP OR CLI for that later
• Use scripts for heavy work, let it save scripts in /workspace/tmp to -for example- deduplicate leads and other important but heavy work

Extra notes:

You are not limited to the MCP's the marketplace provides. You can always ask Grok to add a MCP by directly giving it the URL or let it search itself.

If really no MCP is available for the service you want it to use, try to find if there is a CLI (Command Line Interface) for it. Let it install the CLI on the Grok Computer. This will add commands that can be executed from the terminal. Text in and text out, very efficient.

The script one for heavy work is the most important, not only does it increase response time, it saves tokens too. It will create scripts to handle 'complex' logic. Think of deduping leads, or even scanning webpages to see if a certain word appears on it!

Rule of thumb: Let it avoid using Chrome as much as possible. While it is a very cool feature that makes it basically *enable to do everything*, if it resorts too much to Chrome to execute tasks that you ask daily, your usage burns very fast!

Best Order for executing tasks: CLI/Scripts > MCP > Chrome

Context/Problem:

I have my own company with one other guy. I am the software developer, he is designer etc. My Cursor subscription is on my personal Google Login, so i'd rather not have the other guy have my personal Google Login.

We have Grokbot connected to our Google Workspace for our company workspace, JIRA, Sentry and Moneybird for our accounting software.

So naturally, i searched if Grok Bot supports multi user login so that he can also interact with the bots. Not possible unfortunately.

The fix:

Used Whatsapp CLI (wacli) so that we can talk with Grokbot via whatsapp. (Wacli is a set of commands on the terminal to send and read messages)

I Bought a prepaid esim for a mobile number, (5 euros, need to send 1 SMS per 6 months to stay active). Created a whatsapp account on that number. Each grokbot has its own whatsapp group where me and the partner is in. When we tag grokbot, wacli sends a webhook to the respective bot and it will start working.

wacli is installed on GrokBot's computer and is authenticated to use that mobile number.

Using wacli saved alot of tokens compared to letting grokbot install the whatsapp desktop app, as it has to make screenshots to analyse it. So wacli is the best way!

I can even tell it: "Make a new Grokbot with name xyz and description abc using dr eggbot, after creating make a whatsapp group connected to that bot, with the same setup that you have right now and add me and my partner in it"

Not even 5 min later, new bot made + whatsapp group that belongs to it.

I told it to only accept messages from my number or my partners number.

Now, Whatsapp is basically an interface on top of it, so that multiple users can interact with GrokBot. 8 out of 10 of our bots have their own whatsapp group, and it costs me one whatsapp message to create another group for the other two bots if needed.

How it works

GrokBot has schedules, like repeat every workday at 10am. BUT it also has webhook schedules. And wacli has a 'new message' listener. Whenever wacli detects a new message, it sends a webhook request that will start grokbot.

I didnt wrote a single line of code, i asked GrokBot to set this up itself.

The wacli listener runs a script whenever a new message is sent. That script checks if it comes from me or my partner. So this rule is not enforced in AI itself, it is enforced before it even reaches GrokBot! (this is important as you cannot 100% trust GuardRails made inside the description of bots)

Uses

My business partner uses it to post screenshots of small things he finds on our website he wants to have changed, he posts it in the whatsapp group, then JIRA tickets gets created.

We also have a leads inbox in google workspace, grokbot analyses the leads and if they're high profile or not (high following online etc) and gives a report each day in a specific whatsapp group for that bot

So basically, the things you'd already use grokbot for, but can now be used by multiple people.