Skip to main content

​
Dashboard

CCS ships a routed dashboard, not a one-screen settings modal. The current UI in ccs/cli dev is organized into persistent workspaces with a sidebar, a header utility bar, and direct routes you can bookmark inside the active dashboard session.

​
Open The Dashboard

ccs config
ccs config --host localhost
ccs config --host 0.0.0.0
CCS binds to localhost by default, prints the current session URL, and opens that URL in your browser. When the bind is non-loopback, the dashboard also surfaces remote-access guidance and auth setup expectations.

​
Shell Anatomy

The left sidebar is grouped into four route clusters:
  • General: Home and Analytics
  • Identity & Access: API Profiles, CLIProxy, Copilot, Accounts, Shared Data
  • Compatible CLIs: Claude Extension, Codex CLI, Factory Droid
  • System: Health, Logs, Settings
The current Cursor provider flow lives inside CLIProxy. The older local Cursor IDE bridge survives only as a deprecated compatibility surface.

​
Header Utilities

The top bar carries live utilities that stay visible across routes:
  • connection status
  • language switcher
  • CCS Bar link for the native macOS menu-bar companion
  • docs link
  • GitHub link
  • privacy toggle
  • theme toggle
  • authenticated user menu when dashboard auth is enabled

​
Global Dialogs

OAuth-driven flows can open project-selection and device-code dialogs above the current page without changing your route.

​
Current Route Map

GroupLabelRouteUse it for
GeneralHome/landing stats, live account monitor, logs handoff
GeneralAnalytics/analyticsusage, cost, and session breakdowns
Identity & AccessAPI Profiles/providersAPI and local-model profile CRUD
Identity & AccessCLIProxy Overview/cliproxyOAuth providers, accounts, advanced variants, routing
Identity & AccessAI Providers/cliproxy/ai-providersAPI-key and connector routes inside CLIProxy
Identity & AccessControl Panel/cliproxy/control-panelembedded upstream CLIProxy management center
Identity & AccessGitHub Copilot/copilotcopilot-api install, auth, and daemon status
Identity & AccessCursor Provider/cliproxy?provider=cursorcurrent Cursor OAuth auth, accounts, and provider config flow
Identity & AccessAccounts/accountsCCS auth profiles and continuity lanes
Identity & AccessShared Data/sharedshared commands, skills, and agents
Compatible CLIsClaude Extension/claude-extensionIDE bindings and apply/reset flows
Compatible CLIsCodex CLI/codexCodex diagnostics, control center, raw TOML
Compatible CLIsFactory Droid/droidDroid diagnostics, quick controls, raw JSON
SystemHealth/healthdoctor-style system health and grouped checks
SystemLogs/logsstructured runtime telemetry and legacy errors
SystemSettings/settingssplit-view CCS configuration workspace
DeprecatedCursor IDE Bridge/cursorlegacy local Cursor daemon bridge; use only with ccs legacy cursor
Direct onlyUpdates Center/updatesrollout inbox and support-matrix notices

​
Workspace Notes

​
Home

The home route is an operational landing page:
  • hero counters for profiles, CLIProxy, accounts, and health
  • the live auth monitor with provider drill-down
  • a dedicated handoff card that moves log inspection into /logs
  • an embedded error-log monitor under the fold

​
Identity And Access

This cluster mixes CCS-native profiles and proxy-driven providers:
  • API Profiles is the CRUD workspace for settings-based profiles
  • CLIProxy Overview is the OAuth and variant workspace
  • AI Providers is the API-key and connector workspace inside CLIProxy
  • GitHub Copilot remains a dedicated provider page
  • Cursor now belongs to the CLIProxy provider set; the old Cursor IDE bridge is deprecated compatibility
  • Accounts is the CCS auth-profile workspace
  • Shared Data is the asset browser for commands, skills, and agents
That split matters: CCS auth profiles, API profiles, and CLIProxy provider routes are adjacent in the UI, but they are not the same persistence model.

​
Compatible CLIs

The compatible-CLI pages are dedicated control centers, not generic settings forms:

​
System

The System group now behaves like an operations cluster:
  • Health mirrors ccs doctor status in a rich UI
  • Logs is the dedicated log operations workspace
  • Settings is the split-view configuration surface for global CCS config
If you want to understand…Read this
account-profile workflows and continuityAccounts Workspace
the split-view config surfaceSettings Workspace
OAuth providers, variants, and routingCLIProxy API
API-key and connector routes inside CLIProxyAI Providers Workspace
live auth-state behaviorLive Auth Monitor
log inspection and retention controlsDashboard Logs