How this helps you
One message each morning shows what every Bot is doing and what's waiting on you.
Create a group chat called Daily standup with [Bot names]. Then set up a routine every weekday at [time]: ask the group what each Bot is working on today, what's due, and anything blocked or waiting on me. Summarise it in three lines for me at the end.
Fill in: [Bot names] are the Bots to include. [time] is when your day starts.
What they did
Sonny Sangha keeps a group chat called daily standup with six Bots in it, the maximum at the time he recorded. Every morning a routine has his primary Bot, Chief, ask the group for the daily standup, and each Bot shares what it needs to get done. He says it has stopped him missing events many times. He also asked Chief to create a smaller group chat for his news Bot and script Bot, so a request in that chat wakes whichever Bot is needed without him routing it. For work he can't afford to get wrong, he posts in the group so the Bots check each other.
Who it's for: People running three or more Bots who lose track of what each one is doing.
Before you start
- A primary Bot and at least two other Bots with clear jobs.
- Routines on those Bots, so they have real work to report.
How to try it
- Ask your primary Bot to create a group chat with your main Bots (up to six in Sonny's video).
- Name it something like Daily standup.
- Paste the prompt below into your primary Bot to add the morning routine.
- Read the first few standups and tell Bots to cut anything that isn't useful.
- Create smaller group chats for pairs that often hand work to each other.
What to expect
Each Bot replies in the group with its tasks for the day, and the primary Bot sums up what needs you.
Common mistakes
- Adding every Bot. Each reply uses usage; include the ones with daily work.
- Long replies. Ask for a few lines each.
- Assuming Bots have separate computers. They share one, so two Bots editing the same file can clash.
Related tips
- Use a group thread to watch Bots work together: Put several Bots in one chat so you can see every handoff instead of hidden Bot-to-Bot messages.
- Start with a chief of staff Bot: Talk to one coordinator Bot and let it hand work to your specialist Bots.
- Pick a main Bot so it can see and delegate across your team: A main Bot gets wider visibility into your other Bots, messages you first, and hands work out.
- A manager Bot that never does the work itself: Give a lead Bot one job: break work down, hand it to worker Bots, and check results against the goal. Big projects then run as a chain you only talk to at the top.
- An ops Bot that runs postmortems and daily 1:1s with your Bots: When a Bot makes a mistake, an ops Bot finds the cause, updates the shared playbook and tells the others.
- A Sunday leadership brief from meeting transcripts and Slack: Once a week, a Bot reads your team's meeting transcripts and Slack and tells you what each team discussed, what was decided, and where it drifts from your priorities.
Worth knowingCarved from a segment of this video starting at 18:14. Paraphrased by us; watch the original for the full walkthrough.Next in Multi-bot setups →Move an old AI agent folder into Grok Bot
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot multi-bot setups tips