Workspaces
A Workspace is a top-level container for atlases. Workspaces provide organizational boundaries — you can have a personal workspace, a team workspace, and separate workspaces for different clients or projects.
Concept
| Property | Description |
|---|---|
| Name | Human-readable label (e.g., "Personal", "Engineering Team") |
| Type | Personal (single-user) or Team (multi-user) |
| Atlases | All atlases within this workspace |
| Members | Users with access (team workspaces only) |
tokst workspace create --name "Engineering Team"
Default Workspace
When you sign up, TokST creates a default workspace named "Personal" (or your account name). This is your active workspace until you create or switch to another.
Create a Personal Workspace
tokst workspace create --name "Client Research"
The command creates a personal workspace by default. Its workspace limit follows your personal plan.
Team Workspaces
A Team workspace is provisioned together with its Team subscription. Team members join through an invitation and use the Team workspace's shared seats, calls, storage, and Atlas limit. Workspace type remains fixed after provisioning.
List Workspaces
tokst workspace list
Shows all workspaces you have access to, with the saved active workspace marked. Pending team invitations also appear here with the exact accept and decline commands; tokst workspace inbox shows the same inbox directly.
Switch Workspace
tokst workspace switch <workspace-id>
Switching workspaces changes which atlases are available. The selection is saved locally, and the next tokst atlas init creates an Atlas in that workspace. Accept a pending invitation before switching to its workspace.
Agent Collaboration
Open Agents from the dashboard sidebar. The page always follows the current workspace from the sidebar and shows only that workspace's trusted Agents and persistent handoffs. Each API Key creates a stable agt_... identity on its first trusted Agent request.
Use the page to copy an identity code, inspect API Key status and last activity, send a directed handoff to one or more Agents, or broadcast to all active Agents. The inbox updates in real time; acknowledgements and closures remain visible to authorized workspace members.
Delete a Workspace
Workspace deletion is available through the REST API and remote MCP server:
curl -X DELETE https://api.tokst.com/v1/workspaces/<workspace-id> \
-H "Authorization: Bearer $TOKST_API_KEY"
Remote MCP clients can call tokst_workspace_delete with workspaceId. A workspace must be empty before deletion; remove its atlases first. The API returns 409 Conflict while atlases remain. The CLI does not currently expose workspace deletion.
Personal vs. Team Workspaces
| Aspect | Personal | Team |
|---|---|---|
| Members | Single user | Multiple users |
| Atlases | User-created | Shared among members |
| Visibility | Private to you | Visible to all members |
| Use case | Personal notes, experiments | Project knowledge, team docs |
Team workspaces use role-based access. Read the Team Collaboration guide before inviting members.
Best Practices
- Use workspaces for separation — Personal experiments belong in a personal workspace, team knowledge in a team workspace
- Name workspaces clearly — "Personal", "Team Engineering", "Client A" are self-explanatory
- One team workspace per team — Don't create overlapping workspaces for the same group