Skip to main content
Use chat to work against project files, branches, tasks, GitHub records, App Logs, Feedback, and saved project context without rebuilding that context in each prompt.

Workspace chat

The /dashboard route renders the workspace DashboardPage. It uses the active workspace’s repository, settings, agents, and record sources.

Central Home chat

Central Home renders the dashboard inline when an active thread or draft exists; Home is not highlighted in that state. Before starting a Central draft, select its target workspace.

Thread creation

A draft becomes a thread when its first message is sent. Existing threads retain their original workspace and execution context.

Composer controls

Provider capabilities determine which controls appear. Context-defining choices can lock after the thread starts.

Slash commands

Type / to open grouped entries for actions, models, reasoning levels, runnable workspace commands, agents, and skills. Entries reflect the active workspace and provider capabilities.

Workspace and context locking

Central chat requires a target workspace. That selection scopes files, branches, agents, and record mentions. An existing thread cannot be reassigned to another workspace. See Central versus workspaces.

Side panels

The dashboard panel strip supports Review, multiple browser tabs, Files, and Terminal. Tabs can be reordered and closed; the panel can be expanded, collapsed, or displayed fullscreen beside chat.

Popouts

Open an existing thread or an independent draft in a native desktop window. See Chat Popouts.