Workspace commands.

What a workspace is

A workspace is an addressable context boundary in Empirical. Your personal workspace is for preferences that follow you; a team workspace is for a project, client, product, or temporary collaboration. The active workspace is sent with CLI requests so memory does not silently mix across contexts.

Mental model: Think of a workspace as the filing cabinet an agent is currently allowed to use—not as a second login or a replacement for source control.

When to use a workspace

Create one when several people or agents need the same project context, when client information must stay separate, or when you want a clean context for a demo or experiment.

• Personal: writing style, tooling preferences, and durable defaults
• Project: architecture decisions, deployment rules, and handoff notes
• Client or experiment: intentionally isolated context with its own members

• See how workspace scope affects memory →

Manage the active workspace

Start by inspecting available workspaces and the current selection. select is interactive; use is convenient for scripts and accepts a number, name, or ID.

empirical workspace list
empirical workspace current
empirical workspace select
empirical workspace use "Project Atlas"
empirical workspace create "Project Atlas" --description "Shared engineering context"

Invite people and delete carefully

Invite operations apply to the active team workspace. Deletion is a dry run until --confirm; the default personal brain cannot be deleted. Export anything that must survive before removing a workspace.

empirical workspace invite create --role writer --expires-in-days 7 --max-uses 3
empirical workspace invite list
empirical workspace invite revoke <token>
empirical workspace delete "Project Atlas" --confirm

• Export before cleanup →
• See the short command reference →