Skip to main content

Configuration

CCS uses a unified YAML configuration file. Current schema version: 13.

Config File Location

Config Structure

Key Sections

Config Precedence

Settings are resolved in this order (highest to lowest priority):
For example, --proxy-host overrides CCS_PROXY_HOST, which overrides config.yaml.

Dashboard Management

The easiest way to manage config is through the dashboard:
The dashboard opens in your browser on the current session URL. It provides a GUI for:
  • managing OAuth provider accounts and tokens
  • creating and editing API profiles
  • viewing real-time quota status
  • configuring proxy and advanced settings
API Profiles Configuration

Profile Settings Files

API profiles reference a .settings.json file with environment variable overrides:
All env values must be strings. Booleans or objects will cause crashes on Windows PowerShell.

Environment Variables

Core

Remote Proxy

Integration and Migration

Migration from v1 JSON

If you have a legacy ~/.ccs/config.json, CCS migrates it to config.yaml automatically on first run after upgrade. No manual action needed. To trigger migration manually:

Next Steps

Your First Session

Run a complete first provider flow after configuration

API Profiles

Create profiles for Anthropic, GLM, Kimi, and more

Claude Accounts

Configure multiple Claude account instances

Provider Overview

Compare all supported providers