Workspaces
Use workspaces to separate clients, teams, and operating contexts without losing the shared Kaer shell.
Workspaces are how you keep one Kaer account from turning into a single crowded stream of unrelated work. A workspace can represent a client, a department, an internal function, or a project that deserves its own history and operating surface.
When to split work into a new workspace
Create a new workspace when the work has its own audience, cadence, or ownership. Client delivery is a separate operating context from internal product work. Finance reporting is different from content production. The point is not to create folders for the sake of neatness. The point is to stop conversations, automations, and alerts from blending into each other.
What the cards help you read
The directory shows whether a workspace is active, how many tasks have run there, how many live sessions are open, how many automations exist, and how much token usage has accumulated. That gives you enough context to switch with confidence instead of guessing which operating stream you are stepping into. If the workspace names are clear, the rest of the product becomes easier to read.
A simple way to structure them
Most teams do best when workspace names match real ownership. If a person can answer the question “who is this for and what work belongs here” in one sentence, the split is probably correct. If the answer is fuzzy, you may be creating too many workspaces too early.