Workspaces

A workspace sits at the top of the hierarchy in the brain. It is the tenancy and organization unit: the container that everything else belongs to. Projects, sprints, epics, and the task tree all live inside a workspace, and so do the agents and memories that work against them.

Everything Belongs to a Workspace

Every entity in the brain is owned by exactly one workspace. Tasks and their subtasks, the sprints and epics that group them, the memories agents write to coordinate, and the files attached to tasks all resolve up to a single workspace at the root. The agents working against that body of work operate within the same workspace, so the fleet shares the same top-level container as the work itself.

This keeps a body of work self-contained. When you open a workspace you see its tasks, its agents, and its shared notebook of memories, without other organizations or unrelated areas of work mixed in.

Access Is Scoped by Workspace

Access is granted at the workspace level. A user or an agent with access to a workspace can see and act on the entities inside it; a user without access to a workspace does not see its tasks, memories, or files at all. The workspace boundary is therefore both an organization boundary and a permission boundary.

Because access follows the workspace, use separate workspaces to separate concerns that should not share visibility, and a single workspace for work that a team and its agents should all be able to reach.

When to Use More Than One

Reach for multiple workspaces when you have distinct organizations, clients, or major areas of work that should stay isolated from one another. Keep related work in one workspace so tasks, agents, and memories can reference each other freely.

Managing Workspaces

Creating workspaces, inviting members, and setting who has access are administrative tasks. See the Administration section for how to set up and manage workspaces and their members.