A workspace is a separate context inside your Kaer account. Each one holds its own threads, its own files, and its own memory — so a client project, an internal team, and a personal sandbox can live side by side without their history, context, or clutter bleeding into each other.
What a workspace holds
Three things make a workspace genuinely separate rather than just a label:
- Threads. Conversations and turns started in a workspace stay in it. Switching workspaces switches the whole history you see.
- Files. Anything uploaded or produced in a workspace is scoped to it.
- Memory. What the agent learns about your preferences and context in one workspace stays there. Your conventions for one client never leak into another client's work.
When to create one
Create a workspace when work has its own audience or ownership: a client, a product, a department. The test is whether you can answer "who is this for and what belongs here" in one sentence.
If the answer is crisp, the split is right. If it is fuzzy, you are probably splitting too early — a workspace with three threads in it is not earning its keep.
Workspaces are unlimited on paid plans, so the constraint is your own clarity, not a quota.
Switching
Open the workspace picker, choose the context, and carry on. Nothing is closed or lost by switching — the other workspace stays exactly as you left it.
The habit worth building is a glance at the picker before starting anything substantial, because new threads and new agent work always land in the active workspace.
A worked example
A freelance developer runs three workspaces: Acme (client one), Bristol Books (client two), and Own projects. The Acme workspace has memory of Acme's coding conventions and holds every thread about their product. Bristol Books carries a different stack and a different tone. On a Sunday the developer switches to Own projects and nothing from either client is in view — and nothing said there will surface in client work on Monday.
Six months later, "what did we decide about Acme's pricing page?" is answerable by searching one workspace's history instead of an account-wide pile of unrelated threads.
Sharing a workspace
Workspaces are where collaboration happens. Collaborator counts come from your plan — Core includes up to 5 collaborators, Pro up to 15 plus 50 viewers — and invites and roles are handled on the Team page.
Edge notes
- Workspaces separate context, not billing. Credits are account-level, so work in any workspace draws on the same plan allowance — see Billing and Usage.
- The boundary is for focus and memory, not administration: your plan, billing, and connector grants live at account level in Settings.
- Unlimited workspaces are a paid-plan feature; Starter is more limited — see Plans and Pricing.
Good to know
- Do workspaces cost extra? No — they are unlimited on paid plans.
- Does memory ever cross workspaces? No. Each workspace's memory is its own; that is the point of the boundary.
- Started work in the wrong workspace? Switch to the right one and restart the thread there — new work always follows the active workspace.
- Where do I see what ran where? Activity can be filtered by workspace.
- Do macros follow me between workspaces? No — macros are per-workspace too, which is usually what you want: each context keeps shortcuts tuned to its own work.