My Experience with Grok Bot
This article isn’t a finished text. I’ll keep adding to it as I gain more experience with Grok Bot (a team of AI agents that have their own computer in the cloud and can see a job through to the end). At the top you’ll always find a short summary, “What I know so far”, and when something important changes, that’s the part I’ll rewrite. The sections are organised by topic, not by date. I’ll add individual bots gradually, according to how I actually use them, not all at once. I’m starting with the one I think everyone should start with: dr eggbot. At the end there’s a changelog. When a new part is added, I’ll put a link to that part on social media, not to the beginning of the article. The page address will stay the same.
What Grok Bot is
Most people know AI as a chat: I type a question, get an answer, and then I have to do something with that answer myself. That’s an assistant. It advises, but it doesn’t do anything.
Grok Bot is an agent (an AI that carries out the task itself). It has its own computer in the cloud, a browser and connections to the services I use, such as email, the calendar or online shops. It doesn’t just tell me how I’d do something, it does it: it finds accommodation, fills a shopping cart, adds an event to the calendar, prepares a message or publishes this article on the website. That’s how it reaches into the physical world too: an order arrives at my door as a parcel and a document comes out of my printer.
That’s why one rule applies. Anything with real consequences, like a payment, a sent message or a publication, the bot does only after my explicit yes.

I’ll show concrete examples of real use gradually, with each new bot I add here.
What I know so far
- I started with Grok Bot on the evening of 22 August 2026. The first task was finding a venue for a Brazilian jiu-jitsu (BJJ) training camp. The bot I was talking to that evening is now called Hledač (Czech for “Finder”).
- At first I created new bots through the chief bot. Before I brought in dr eggbot, I had around twenty-five of them, and some overlapped or didn’t have their job properly described.
- Dr eggbot first spoke up on 31 October 2026. Since 1 November I’ve been creating and editing all my bots through it.
- On 3 November we cleaned up the fleet: we merged bots that were doing the same work, and retired the ones that didn’t have a real role.
- Each bot should do one job. Payments, messages and emails each have their own bot, and nothing goes out without my approval.
- I talk to the bots in Czech. Their internal instructions are written in English, because that uses fewer tokens (the units AI uses to measure text and cost) each time they start up. Since 13 November it’s a firm rule that they always speak Czech with me, including on voice calls.
How I started
I didn’t start with a plan for a team of bots. On Saturday 22 August 2026 at 22:15 I opened a chat with a new bot. The first thing I asked was whether we could speak Czech. We could.
That same evening I gave it its first real task: I was looking for accommodation for a weekend Brazilian jiu-jitsu camp, with a gym, full board and a place to swim, within reach of Frýdek-Místek, including across the border if needed. The bot only got the name Hledač much later.
I created the chief bot (it’s now called Robin Javorek - AI agent) on 31 August. Through it I then added more bots: for mail, for the calendar, for Instagram, for shopping. It went quickly, and after two months I had around twenty-five. It worked, but it was messy. Some stepped on each other’s work, some had almost nothing in their description, and others had long manuals that loaded every time they woke up.

Dr eggbot
Dr eggbot is a bot that designs and creates other bots. It asks a few questions about what the new bot should be and what it should not be, then creates it. It also revises the ones that already exist: it shortens their brief, merges overlaps and removes whatever has no job.
The template was designed by Lauren Tan. She works directly on Grok Bot at SpaceX Super Intelligence and on GitHub is listed as a software engineer at xAI. She previously worked at Cursor, Meta and Netflix, and is part of the React Compiler core team. On the official Grok Bot marketplace the template is listed under her name, and she herself writes that eggbot is her bot designer, the one she uses to create new bots.
If I were starting again, I’d start with it. I didn’t. First I multiplied bots through the chief bot, and only then did I get someone to make sure each one has a single, clear job. I could have avoided the cleanup that followed.
How it works in practice
I say what I need. Eggbot first assesses whether a new bot should be created, or whether it’s enough to adjust one I already have. It asks a few short questions. Only then does it create the bot and give it an icon so it can be recognised in the list. Sometimes it talks me out of a new bot, because the task is a one-off.
The first major job with it wasn’t creating bots, but a cleanup. On 3 November, on its recommendation, we cleaned up the whole fleet. We merged, for example, product search and filling the shopping cart into Hledač, presentations and graphics into Kreativec, and editing reels (short Instagram videos) into the club’s Instagram bot. In the app, I deleted the bots that no longer had a job of their own. That same day I also gave Hledač the daily tips on family events, which a separate bot had been doing before.
Then more bots started being added through it. Each will get its own section when its turn comes.
Since then, eggbot also watches over the fleet. On weekdays it goes through the other bots’ chats and looks for places where I got stuck or had to fix something. If it finds nothing, it stays quiet. If it finds something, it proposes a change and waits for my yes. That’s also how the rule that they all speak only Czech with me came about: it wasn’t working on calls, so on 13 November we wrote it in as a hard rule.
Changelog
- 17 November 2026: first version. How the article is meant to work, what Grok Bot is and how an agent differs from an assistant, how I started, and the first bot, dr eggbot.