Claude follows your workspace
One connector connection for the whole agency — switch client in the app and Claude moves with you.
The obvious worry about running many clients through one Claude connection is that you'd have to reconnect every time you changed client. You don't.
You connect Claude once. It always works in whichever workspace you're currently in.
How it works
Switch client in the app
Use the workspace switcher in the sidebar, exactly as you would to work in the app.
Go back to Claude
Nothing to reconnect, no setting to change, no need to start a new chat.
Claude is now working on that client
From your next message, it reads that client's products, brand voice, branding and Brain — and anything it creates lands in their workspace.
Your connection isn't tied to one client. It reads which workspace you're in each time you send a message.
Knowing which client Claude is on
Ask Claude to list your products. It reports the workspace those products came from, names the other workspaces on your account, and links you to the switcher.
The same happens when you create a product — Claude confirms which client it was created for, so a product built against the wrong workspace doesn't go unnoticed.
If you ask for a product from another client
Claude will tell you. Because a connection only reaches the workspace it's currently in, asking it to edit a product belonging to another client returns an explanation rather than a dead end: which workspace it's looking in, which other workspaces exist on your account, and a link to switch.
Switch in the app, come back, and ask again — nothing to reconnect.
Switching from inside Claude
Not yet. Today the switch happens in the app and Claude follows.
Asking Claude to "switch to client B" won't move it, because the connector has no tool for changing workspace — that's a planned addition, and it will arrive with a future update to the connector.
If you work in two clients at once
Claude works in whichever workspace you switched to most recently. If you're moving between clients quickly, the safe pattern is one client per sitting: switch, confirm with a product list, build, then switch.
Using a key for a single client
If you'd rather have a connection that's permanently locked to one client — for a build machine or an automation that should never touch anything else — an API key can be pinned to a single workspace, and it ignores whatever you're doing in the app. Keys are managed under Settings → API.
For everyday agency work, the normal Claude connection following the app is what you want.