First Session

After installing CCS, run your first session in under 2 minutes.

Step 1: Choose a Provider

Default Claude (OAuth)
Codex (OAuth)
Kiro (Free tier)
API Profile

# Browser opens for Claude OAuth
ccs

Requires a Claude Pro or Max subscription.

# Browser opens for OpenAI OAuth
ccs codex "review this code"

Works well as a first browser-OAuth route.

# Device code flow (no browser required)
ccs kiro "help me debug this"

Free tier via AWS Builder ID.

# Z.AI GLM — requires API key setup first
ccs glm "quick code fix"

See API Profiles for setup.

Other supported routes such as GHCP, Gemini, iFlow, and Antigravity are documented in Provider Overview. This page keeps the first-run path focused on the safest baseline examples.

Step 2: Authenticate

On first run, CCS triggers OAuth automatically.

Browser opens

CCS spawns a local OAuth callback server and opens the provider login page. For Device Code providers (Kiro, Kimi), a code and URL are shown in the terminal instead.

Complete login with the account for your chosen provider.

Token saved

OAuth credentials are cached at ~/.ccs/cliproxy/auth/. Future runs skip this step.

Session starts

CCS launches the selected target runtime with the chosen provider injected as the API backend. By default, that target runtime is Claude Code.

Step 3: Start Coding

# Interactive session (default)
ccs codex

# One-shot with prompt
ccs kiro "what does this regex do: ^[a-z]+$"

# Pass a prompt directly
ccs glm "refactor this function to use async/await"

How Profile Switching Works

Each ccs <profile> command injects different environment variables into the active target runtime:

ccs codex   →  ANTHROPIC_BASE_URL=http://127.0.0.1:8317/api/provider/codex
ccs kiro    →  ANTHROPIC_BASE_URL=http://127.0.0.1:8317/api/provider/kiro
ccs glm     →  ANTHROPIC_BASE_URL=https://api.z.ai/api/anthropic
ccs         →  Default Claude account (no proxy)

Switching takes under 1 second. Running ccs codex in one terminal and ccs glm in another keeps those sessions separate and avoids conflicts.

Dashboard

Open the visual configuration dashboard at any time:

ccs config

The dashboard shows all profiles, OAuth provider status, quota usage, and lets you manage API keys without editing files.

Quick Examples

# Switch between providers instantly
ccs "design the auth layer"         # Default Claude
ccs glm "implement user service"    # Z.AI GLM (cost-optimized)
ccs codex "security review"         # OpenAI Codex

# Extended thinking / reasoning
ccs --effort high "debug this regression"
ccs codex --effort xhigh "complex refactor"
ccs km "reason through this architecture change"

# Multi-account: work vs personal
ccs work "review PR #123"
ccs personal "help with side project"

Next Steps

All Providers

Compare OAuth providers, Claude accounts, and API profiles

Configuration

Config file format, precedence rules, and env vars

Claude Accounts

Run multiple Claude subscriptions simultaneously

API Profiles

Bring your own API keys

Getting Started

Providers

Features

Tutorials

First Session

First Session

Step 1: Choose a Provider

Step 2: Authenticate

Step 3: Start Coding

How Profile Switching Works

Dashboard

Quick Examples

Next Steps

All Providers

Configuration

Claude Accounts

API Profiles

​First Session

​Step 1: Choose a Provider

​Step 2: Authenticate

​Step 3: Start Coding

​How Profile Switching Works

​Dashboard

​Quick Examples

​Next Steps

All Providers

Configuration

Claude Accounts

API Profiles

First Session

Step 1: Choose a Provider

Step 2: Authenticate

Step 3: Start Coding

How Profile Switching Works

Dashboard

Quick Examples

Next Steps