Skip to main content
Select a workspace to keep chat, code, tasks, GitHub records, and product signals attached to the repository that owns them.

​
Definition

A workspace is the project boundary around one local folder. For the corresponding Central layer, see Central versus workspaces.

​
Workspace-owned data

​
Central’s exact role

Central is not uniformly an aggregation layer. Some pages aggregate workspace records, some reuse a component with different context, Central Terminals uses its own synthetic context, and Central settings are app-wide. The exact behavior is in Central versus workspaces.

​
Route and surface matrix

​
Switching workspaces

Select a workspace in the rail before opening a workspace route. The active workspace supplies the repository root and the project IDs used by its pages and chat.

​
Workspace folders

Use the dashed + button at the bottom of the workspace rail and select New folder. Rename folders, assign or remove logos, reorder folders and workspaces, and drag workspaces into or out of folders. Deleting a folder removes the grouping, not its workspaces.

​
Local and server synchronization

Folder layout is applied locally first, then synchronized to the desktop server for paired mobile clients. The server persists the document at:
Folder metadata is not stored in Supabase.

​
Settings scope

Use Workspace settings for repository-specific controls and Central settings for app-wide controls.