How I multi-task with @bot: 1. Tell your agent to keep work organized in a Notion database and take detailed notes about progress/blockers/etc. in each page. 2. Yeet tasks into chat (manually, or automatically pull from email/sentry/github/etc. with routines)—most of the time these init a Cursor cloud session to automatically start building/fixing. This has been the best way for my bot to work on multiple things at the same time while keeping visibility into what's flowing through the…
I've been using Notion databases as a project/task tracker for Grok Bot and it just like, works really well...ezmode.
📝 How I run multiple teams of Grok Bots 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 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! The roster lives in that channel. 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 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. 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? https://x.com/i/article/2092982704329605…
Related profile searches
Building @EurekaLabsAI. Previously Director of AI @ Tesla, founding team @ OpenAI, CS231n/PhD @ Stanford. I like to train large deep neural nets.
ML/AI research engineer. Ex stats professor. Author of "Build a Large Language Model From Scratch" (https://amzn.to/4fqvn0D) & reasoning (https://mng.bz/lZ5B)
Chief Scientist, Google DeepMind & Google Research. Gemini Lead. Opinions stated here are my own, not those of Google. TensorFlow, MapReduce, Bigtable, ...