Skip to main content
Use a workspace when the action belongs to one repository; use Central when you need a cross-workspace view or an app-wide setting. A Central route is not automatically an aggregate—the matrix below identifies the actual behavior.

​
Mental model

​
Route matrix

The default workspace sidebar lists Home, Tasks, GitHub, App Logs, Feedback, Analytics, Calendar, Notebook, Automations, Agents, and Project. The default Central sidebar lists Home, Tasks, App Logs, Feedback, Analytics, Calendar, GitHub, and Skills. Central Terminals is opened from the Central terminal control rather than the editable Central navigation list.

​
True aggregate twins

Central Home, Tasks, App Logs, Feedback, Analytics, Calendar, and GitHub combine data from multiple workspaces. Their records retain workspace or project context so opening, editing, executing, or triaging a record targets its owner.
Central Analytics adds each site’s visitors value. It does not deduplicate the same person across sites, so its visitor total is the sum of per-site unique visitors rather than an account-wide unique-person count.

​
Same-component twins

Central Skills directly re-exports the workspace Skills page. It is a shared implementation, not a precomputed cross-workspace feed. Workspace-local skill discovery depends on workspace context, and starting a chat requires a workspace target. Central Terminals is also not an aggregate. It owns an independent terminal canvas under the synthetic workspace ID __central__ and exposes only Split and Canvas as its top-level modes.

​
Central-only settings

Open Central Settings for app-wide configuration. These destinations have no per-workspace equivalent: See Central Settings for every control.

​
Workspace-only surfaces

Notebook, Automations, Agents, and Project exist only in a selected workspace. Their settings and files belong to that repository context. Workspace settings also own repository defaults, instructions, Git behavior, task execution defaults, environment files and actions, project credentials, integrations, local MCP servers, monitor setup, and archived threads. See Workspace Settings for the complete settings order.

​
Switching and context

Selecting a workspace changes the repository path, project name, files, agents, branches, tasks, and project-backed monitor records used by workspace pages. A Central record retains its owner; actions resolve that owner before operating. Central Home is the exception that can become the normal Dashboard inline. Selecting a thread or entering draft mode mounts the Dashboard, and the Central composer persists its chosen target workspace.

​
GUI Lifetime gating

GUI Lifetime removes hosted monitoring surfaces while retaining local workspace functionality. Tasks, GitHub, Calendar, Automations, Agents, Notebook, Project, local terminals, local MCP servers, Providers, Connections, Appearance, and Keybinds remain local/app functionality.