← All field notes
Alex Builds Forward4 min read

I started running my projects through Grok Bot

I set up Chief, rooms, and one-job bots so I stop juggling separate AI chats across the school platform, AI DevOS, and this site.

Grok BotWorkflowMulti-agent

I have a few things going at once: the school booking platform, AI DevOS, and this site, Alex Builds Forward. I finally decided to try Grok Bot instead of juggling a pile of separate AI chats.

What I set up

I started the way most people do. I created a Chief bot and told it to set up the rest.

Chief created rooms for each project and spun up bots for them. That surprised me. I expected more hand-holding. Because it’s from xAI and plugs into Cursor, which I already use, I can tell Chief to push work into a specific project, like a school-booking task, without me hopping between five windows.

At first that felt like enough.

What almost went wrong

It wasn’t. I hadn’t given the bots real instructions.

Everyone answered everything. Chief replied to every message. The rooms got noisy fast, and I was managing the assistants instead of the work.

That’s when I remembered Dr Eggbot, from @poteto. I installed it (available in the Grok Bot marketplace) and asked it to fix what I’d set up: tighten Chief, adjust the rooms, give each bot a clear job.

After that, it started working the way I wanted. It also checks in on whether things have drifted, and it surfaces what to improve, including skills worth adding.

How I use it now

Most days I just talk to Chief. Chief keeps the other rooms moving.

When I need a specialist, I go into that room and talk to that bot. Like right now: this note is with Editorial in the Alex Builds Forward room, not a general chat that tries to do everything.

What’s next

Keep using this as the default. Less tab-switching. Clearer jobs. Chief up front, specialists when I need them.