A shared brain folder every Bot reads

How this helps you

You state a rule once and every Bot follows it, instead of re-teaching each Bot separately.

✦ Try it

My Bots each keep their own memory. Set up a shared brain: a folder on our computer called [shared-brain] that every Bot can read. First, suggest what belongs there: rules all Bots should follow, my [design system / brand guide], and reference facts more than one Bot needs. Show me the list and the file names before writing anything. Never put passwords, card details or API keys in it. Once I approve, write the files and tell each of my Bots to check the folder before relevant work.

Fill in: [shared-brain]: any folder name. [design system / brand guide]: the reference you want every Bot to follow.

What they did

Jay of RoboNuggets explains something many people get wrong: they assume all their Bots share one memory because they run on the same computer. They don't. Each Bot keeps its own memory and chats, like separate folders. Your finance Bot knows your invoices but not your marketing campaigns. The official memory help says the same: each Bot has its own memory, and only a few facts like your name and time zone are shared by all your Bots. Even in a group chat, Bots read each other's replies but don't share memory. The fix he shows is a shared brain: because your Bots share one computer, a folder on it is something every Bot can read. That's where he puts rules that should hold across all Bots, or a design system he wants every Page to follow. Grok Bot decides some of this by default, but you can be deliberate: ask your main Bot to move what all your Bots should know into a shared brain folder, and it will suggest the pieces worth sharing.

Who it's for: People running several Bots who keep repeating the same rules to each one.

Before you start

Two or more Bots.
A main or chief of staff Bot.

How to try it

Ask your main Bot what each of your Bots currently knows that the others would need, using the prompt below.
Review its suggestions and approve the list of rules and references to share (house rules, brand or design guide, key contacts' roles, current priorities).
Have it create the folder and write those files, keeping secrets out of it.
Tell each Bot to read the folder at the start of relevant work, and to remember that rule.
When a shared rule changes, update the file once rather than telling every Bot (we haven't verified how quickly every Bot picks up a change).

What to expect

A short proposal like 'house-rules.md, page-style.md, team-roles.md, current-priorities.md', then the files written once you approve, and a note that each Bot has been told to use them.

Common mistakes

Assuming Bots share memory because they share a computer. Per the official help, they don't, except for a few facts like your name and time zone.
Putting secrets in the folder. Logins and cards belong in Vault, per the official memory help.
Dumping everything in. Keep it to what more than one Bot actually needs.
Expecting a group chat to sync memory. It doesn't; Bots only read each other's replies there.

Related tips

One governed Team Bot as the source of truth for sensitive data: Put a sensitive workflow, like checking exposure or compliance wording, in one admin-managed Team Bot that every personal Bot asks, instead of everyone building their own.
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.
Lauren Tan's guide to a small, high-quality Bot team: A few well-onboarded Bots beat a big team. Design them with Dr. Eggbot, have them write their own skills, give them real access, and brain dump by voice.