Work
One group-chat room per project; Notion when seats fill
One mega-agent chat becomes the brain and every project collides.
What hurt
Chuck Gibson (@ChuckHTF) found Grok Bot useful when group chats arrived. Pattern: not one agent for everything — a room per project (Specialist Desk, Brick Block, Passive income, Multifamily search). Seat the bots that own the work in one thread with clear lanes. Each agent still has its own computer; the group chat is the stand-up, not the brain. When a room hits the seat limit, Notion stays the source of truth.
What to install or create
Name rooms by project. Seat only the owning bots. Keep durable state in each bot computer + Notion when over seat limit. Use the room for handoffs and stand-up, not as the only memory.
Bots
Project seats
Only the bots that own that project's work sit in the room.
Plugins
None on day one. Follow the first-run steps.
Files
Notion page as source of truth when the room hits the seat limit.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/ChuckHTF/status/2098554295868104854 for the room pattern.
- 2Create one group chat per project. Name it after the project, not "everything".
- 3Seat only the bots that own that work. Clear lanes; each keeps its own computer.
- 4Treat the room as stand-up / handoff — not the only brain.
- 5When you hit the seat limit, park durable state in Notion and keep the room light.
Approval fence
No send, post, or spend from the room without your yes. Notion writes stay behind approval if irreversible.
What to tweak
Steal room-per-project + standup-not-brain + Notion overflow. Complements job-named seats.
Source
Chuck Gibson @ChuckHTF · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.