How to use Claude Projects to get automatic client switching, persistent context, and a clean mental separation between clients.
The Pattern
Create one Claude Project per client. Add a single instruction that tells Claude to switch to that client's Armbrain client mind automatically. Every conversation in that project starts in the right context -- no manual switching needed.
This works in both Claude Desktop and claude.ai (Teams/Pro plans with Projects enabled).
Setup (2 Minutes Per Client)
1. Create a Claude Project
In Claude Desktop or claude.ai:
- Click New Project (or the
+next to Projects) - Name it after your client (e.g., "Julica" or "Acme Corp")
2. Add the Auto-Switch Instruction
Open the project settings and find Project Instructions (sometimes called "Custom Instructions" or "System Prompt"). Add this as the first line:
Always switch to [Client Name] in Armbrain at the start of every conversation.For example:
Always switch to Julica in Armbrain at the start of every conversation.Save the instructions.
3. Start a New Chat in That Project
Open a new conversation inside the project. Claude will automatically call switch_client and you'll see confirmation that you're in the right client mind. You're ready to work.
Why This Works
- Automatic context. Every new chat in the project starts in the right client mind. No more "switch to Acme" at the start of every conversation.
- Mental separation. Your Julica conversations are in the Julica project. Your Acme conversations are in the Acme project. No confusion about which client you're working on.
- Searchable history. Claude's project view groups all conversations by client. You can scroll back to find that email you drafted or that strategy discussion.
- Shareable setup. If you have a VA or team member, they can use the same project instructions to get the same automatic switching.
Power Tips
Add client-specific instructions
The project instructions field is a great place for per-client preferences:
Always switch to Julica in Armbrain at the start of every conversation.
When writing emails for Julica, always include the standard disclosure statement.
Bobby prefers short, direct emails -- no fluff.
Diana handles operations; Bobby handles sales and partnerships.These instructions apply to every conversation in the project, so Claude always has this context.
Use the armbrain / cm / cmo shortcut
In any chat -- inside a project or not -- you can begin a message with armbrain, cm, or cmo and Claude treats it as an Armbrain request (e.g. cm prep me for the Acme meeting). It works as soon as you're connected, and only fires when the word is the very first thing in the message. To make cm / cmo even more dependable for a single client, add this line to the project instructions:
When my message starts with "armbrain", "cm", or "cmo", treat it as an Armbrain request and use the Armbrain tools to answer it.Add recommended tools
If your Claude plan supports it (Teams/Enterprise), you can add MCP tools as recommended for the project. This makes Armbrain tools appear prominently in the tool picker.
Combine with personal preferences
Your global Claude preferences (Settings > Personal Preferences) apply across all projects. Use that for things that apply everywhere:
Never use em dashes in writing.
Today's date is always available -- don't ask me for it.
When I say "draft an email," always show me the draft before sending.Client-specific preferences go in the project instructions. Global preferences go in personal settings.
One project for general CMO work
Create a project called "CMO General" or "Cross-Client" for work that spans multiple clients -- weekly reviews, cross-client summaries, prospecting. Don't add an auto-switch instruction here. Instead, switch manually as needed.
What This Doesn't Do
- It doesn't prevent switching. You can still say "switch to Bluebell" inside a Julica project. The instruction just sets the default.
- It doesn't sync the project name with the client mind name. If you rename the project or the client mind, update the instruction manually.
- It doesn't show a persistent indicator. Claude Desktop doesn't have a permanent "active client mind" badge. You'll see the switch confirmation at the start of each chat, but not a persistent label. (This is a known gap we're working on.)
Recommended Project Layout
| Project Name | Auto-Switch Instruction | Purpose |
|---|---|---|
| Julica | "Always switch to Julica in Armbrain" | All Julica client work |
| Acme Corp | "Always switch to Acme Corp in Armbrain" | All Acme client work |
| Tech Fluency | "Always switch to Tech Fluency in Armbrain" | All Tech Fluency client work |
| CMO General | (none) | Cross-client reviews, prospecting, admin |
Troubleshooting
Claude doesn't switch automatically
Make sure the instruction is the first line in project instructions. If it's buried below other text, Claude may not prioritize it. Also verify the client name matches exactly -- Armbrain does fuzzy matching, but "Julica Inc" won't match "julica" if they're too different.
"No client selected" errors mid-conversation
Long conversations sometimes lose tool state. If you see this, just say "switch to [client name]" to re-establish context. This is a Claude session limitation, not an Armbrain issue.
I want to switch clients within a project
Just say "switch to [other client]." The auto-switch instruction only fires at conversation start. Mid-conversation switches work normally.
Related Guides
- Client Management -- creating and configuring client minds
- Client Onboarding -- setting up a new client from scratch
- Using Armbrain from claude.ai -- browser-based access
- Personal Mind and CMO Voice -- your personal preferences client mind