Skip to main content

​
Settings Workspace

The Settings workspace at /settings is the dashboard’s routed configuration surface. On desktop it uses a split view: form-based controls on the left, a live read-only snapshot of ~/.ccs/config.yaml on the right.

​
Access

ccs config
# Sidebar -> System -> Settings
# Direct route -> /settings

​
Current Layout

​
Desktop

  • Left panel: tabbed configuration sections
  • Right panel: config.yaml viewer with copy and refresh actions
  • Resize handle: lets you rebalance forms vs raw config

​
Mobile

The page collapses into a stacked layout. The raw config.yaml viewer drops behind the active section so the forms stay usable on narrow screens.

​
Current Tabs

TabWhat it managesRelated doc
WebSearchprovider readiness, API keys, install hints, and CCS search routingWebSearch
ImageMCP-first image analysis state, repair actions, and profile coverageImage Analysis
Channelsofficial-channel selection, token status, and launch previewCLI Commands
Envtop-level global environment variables saved in CCS configConfiguration
Thinkingthinking mode, overrides, tier defaults, and provider overridesExtended Thinking
Proxylocal vs remote CLIProxy server settings and connectivityRemote Proxy
Authdashboard authentication enablement, secret generation, and statusDashboard Authentication
Backupsbackup inventory, restore, and cleanup workflowsFile Locations

​
Raw Config Pane

The right-hand pane is a viewer, not a second editor:
  • shows the current ~/.ccs/config.yaml
  • supports copy and refresh actions
  • helps you verify what the forms actually persisted
If the file does not exist yet, the workspace points you back to: 
ccs migrate

​
Operational Notes

  • Section content is lazy-loaded, so the active tab can recover independently if one section fails
  • Structured settings stay in the form controls; raw YAML remains read-only in this workspace
  • The page is route-aware, so you can bookmark /settings directly inside the current dashboard session

​
When To Use This Page

Use the Settings workspace when the change belongs to shared CCS behavior:
  • search and image-analysis tooling
  • announcement and support channels
  • global env defaults
  • proxy topology
  • dashboard auth
  • backup hygiene
Use the profile workspaces instead when the change is specific to one provider or one compatible CLI.