How I run multiple teams of Grok Bots

106K
703
38
50
1.5K

TL;DR

Eric Zakariasson shares an experimental setup using Notion to manage teams of Grok Bots, treating AI agents like human employees with specific roles, task boards, and a project manager bot.

Most of the time I run my Grok Bots as separate chats. Coder in one, Writer in another, Researcher in a third. That's all fine until you need juggle couple of different projects at the same time. It becomes hard filter out signal from noise, and keeping them in sync.

As a human and a team of humans, we tend to coordinate work in projects. Each project gets a spec, plan, perhaps a Slack channel to communicate in. Then for each project, you'd have different tasks that someone takes on.

So, I replicated that. Each project gets a Grok Bot channel and an entry in a Notion database. Note that this is an experimental pattern I'm still trying out

eric zakariasson - inline image

The setup

I created two databases in Notion, Projects and Tasks. Then, I created a projects (plural) Manager bot. This will take care of the higher level coordinate of projects and tasks. It has a /Project Ops skill that takes care of creating a project, opening a channel, and staffing it with the right bots. It's responsible for the meta work.

One project equals one channel in the sidebar, and the channel has the team of bots (and me) in it!

eric zakariasson - inline image

The roster lives in that channel.

eric zakariasson - inline image

Staffing rules I added:

  • Reuse existing bots first. This can be a Coder, Researcher, Writer or anything else that I've already defined.
  • Propose at most five bots besides the PM. Each channel is limited at six bots (just an arbitrary number I came up with)
  • Create a new bot only when nothing on the bench fits, and only after I say yes. This could be a specialist in a domain that gets reused in the future, or en ephemeral one only for this project.

Here's what the Projects database looks like

eric zakariasson - inline image

How I use it

Once the channel exists, I talk in it with the roster and we scope out the tasks for the project.

The PM sits in the channel too, but mostly watches progress and makes sure the databases are up to date.

When a bot gets stuck, or needs more input, it'll mark its task as Blocked and then ping me in the channel. Often the bots can accomplish a lot on their own, and I can just watch the cards getting move around. Quite satisfying to be honest.

eric zakariasson - inline image

The interesting part is that the more I build on this, the more it resembles a system initially built for humans. A board, a manager, specialists claiming tasks, a blocked column, a channel.

That is the experiment so far. If you run a team of bots, I want to see your setup! How do you run yours?

Rielabora in YouMind

Turn one viral article into a full content workflow

Collect the source, decode the pattern, create assets, draft the story, and distribute from one AI workspace.

Explore YouMind
Per i creator

Trasforma il tuo Markdown in un articolo 𝕏 pulito

Quando pubblichi i tuoi testi lunghi, formattare immagini, tabelle e blocchi di codice per 𝕏 è una seccatura. YouMind trasforma un'intera bozza Markdown in un articolo 𝕏 pulito e pronto da pubblicare.

Prova Markdown verso 𝕏

Altri pattern da decodificare

Articoli virali recenti

Esplora altri articoli virali