ccs/README.md

CCS - Claude Code Switch

Languages: English | Tiếng Việt

Switch between Claude Sonnet 4.5 and GLM 4.6 instantly. Use the right model for each task.

The Problem: You have both Claude subscription and GLM Coding Plan. Two scenarios happen daily:

1. Rate limits: Claude hits limit mid-project, you manually edit ~/.claude/settings.json to switch
2. Task optimization: Complex planning needs Claude Sonnet 4.5's intelligence, but simple coding works fine with GLM 4.6

Manual switching is tedious and error-prone.

The Solution:

ccs son       # Complex refactoring? Use Claude Sonnet 4.5
ccs glm       # Simple bug fix? Use GLM 4.6
# Hit rate limit? Switch instantly:
ccs glm       # Continue working with GLM

One command. Zero downtime. No file editing. Right model, right task.

Quick Start

Install:

macOS / Linux:

curl -fsSL ccs.kaitran.ca/install | bash

Windows PowerShell:

irm ccs.kaitran.ca/install.ps1 | iex

Configure:

# Edit with your profiles
cat > ~/.ccs/config.json << 'EOF'
{
  "profiles": {
    "glm": "~/.ccs/glm.settings.json",
    "son": "~/.ccs/sonnet.settings.json",
    "default": "~/.claude/settings.json"
  }
}
EOF

Use:

ccs          # Use default profile
ccs glm      # Use GLM profile
ccs son      # Use Sonnet profile

Why CCS?

Built for developers with both Claude subscription and GLM Coding Plan.

Two Real Use Cases

1. Task-Appropriate Model Selection

Claude Sonnet 4.5 excels at:

• Complex architectural decisions
• System design and planning
• Debugging tricky issues
• Code reviews requiring deep reasoning

GLM 4.6 works great for:

• Simple bug fixes
• Straightforward implementations
• Routine refactoring
• Documentation writing

With CCS: Switch models based on task complexity, maximize quality while managing costs.

ccs son       # Planning new feature architecture
# Got the plan? Implement with GLM:
ccs glm       # Write the straightforward code

2. Rate Limit Management

If you have both Claude subscription and GLM Coding Plan, you know the pain:

• Claude hits rate limit mid-project
• You manually copy GLM config to ~/.claude/settings.json
• 5 minutes later, need to switch back
• Repeat 10x per day

CCS solves this:

• One command to switch: ccs glm or ccs son
• Keep both configs saved as profiles
• Switch in <1 second
• No file editing, no copy-paste, no mistakes

Features

• Instant profile switching (Claude ↔ GLM)
• Pass-through all Claude CLI args
• Smart setup: detects your current provider
• Auto-creates configs during install
• No proxies, no magic—just bash + jq

Installation

One-Liner (Recommended)

macOS / Linux:

# Short URL (via CloudFlare)
curl -fsSL ccs.kaitran.ca/install | bash

# Or direct from GitHub
curl -fsSL https://raw.githubusercontent.com/kaitranntt/ccs/main/install.sh | bash

Windows PowerShell:

# Short URL (via CloudFlare)
irm ccs.kaitran.ca/install.ps1 | iex

# Or direct from GitHub
irm https://raw.githubusercontent.com/kaitranntt/ccs/main/install.ps1 | iex

Note:

• Unix installer supports both direct execution (./install.sh) and piped installation (curl | bash)
• Windows installer requires PowerShell 5.1+ (pre-installed on Windows 10+)

Git Clone

macOS / Linux:

git clone https://github.com/kaitranntt/ccs.git
cd ccs
./install.sh

Windows PowerShell:

git clone https://github.com/kaitranntt/ccs.git
cd ccs
.\install.ps1

Note: Works with git worktrees and submodules - the installer detects both .git directory and .git file.

Manual

macOS / Linux:

# Download script
curl -fsSL https://raw.githubusercontent.com/kaitranntt/ccs/main/ccs -o ~/.local/bin/ccs
chmod +x ~/.local/bin/ccs

# Ensure ~/.local/bin in PATH
export PATH="$HOME/.local/bin:$PATH"

Windows PowerShell:

# Create directory
New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.ccs"

# Download script
Invoke-WebRequest -Uri "https://raw.githubusercontent.com/kaitranntt/ccs/main/ccs.ps1" -OutFile "$env:USERPROFILE\.ccs\ccs.ps1"

# Add to PATH (restart terminal after)
$Path = [Environment]::GetEnvironmentVariable("Path", "User")
[Environment]::SetEnvironmentVariable("Path", "$Path;$env:USERPROFILE\.ccs", "User")

Upgrade

macOS / Linux:

# From git clone
cd ccs && git pull && ./install.sh

# From curl install
curl -fsSL ccs.kaitran.ca/install | bash

Windows PowerShell:

# From git clone
cd ccs
git pull
.\install.ps1

# From irm install
irm ccs.kaitran.ca/install.ps1 | iex

Note: Upgrading preserves your existing API keys and settings. The installer only adds new features without overwriting your configuration.

Configuration

The installer auto-creates config and profile templates during installation:

macOS / Linux: ~/.ccs/config.json Windows: %USERPROFILE%\.ccs\config.json

macOS / Linux Configuration

Uses settings file paths:

{
  "profiles": {
    "glm": "~/.ccs/glm.settings.json",
    "sonnet": "~/.ccs/sonnet.settings.json",
    "default": "~/.claude/settings.json"
  }
}

Each profile points to a Claude settings JSON file. Create settings files per Claude CLI docs.

Windows Configuration

Important: Windows Claude CLI uses environment variables instead of --settings flag.

Windows uses the same file structure as Linux, but settings files contain environment variables:

Config format (~/.ccs/config.json):

{
  "profiles": {
    "glm": "~/.ccs/glm.settings.json",
    "son": "~/.ccs/sonnet.settings.json",
    "default": "~/.claude/settings.json"
  }
}

GLM profile (~/.ccs/glm.settings.json):

{
  "ANTHROPIC_BASE_URL": "https://api.z.ai/api/anthropic",
  "ANTHROPIC_AUTH_TOKEN": "your_glm_api_key",
  "ANTHROPIC_MODEL": "glm-4.6",
  "ANTHROPIC_DEFAULT_OPUS_MODEL": "glm-4.6",
  "ANTHROPIC_DEFAULT_SONNET_MODEL": "glm-4.6",
  "ANTHROPIC_DEFAULT_HAIKU_MODEL": "glm-4.6"
}

Claude profile (~/.ccs/sonnet.settings.json):

{
  "env": {}
}

How it works:

• CCS reads the settings file for the selected profile
• Temporarily sets environment variables from the settings file
• Executes Claude CLI with those variables
• Restores original environment variables after execution

Compatibility: Settings files support both direct format (Windows) and {"env": {...}} wrapper (Linux compatibility).

Usage

Basic

# Works on macOS, Linux, and Windows
ccs           # Use default profile (no args)
ccs glm       # Use GLM profile
ccs son       # Use Sonnet profile

Windows Note: Commands work identically in PowerShell, CMD, and Git Bash.

With Arguments

All args after profile name pass directly to Claude CLI:

ccs glm --verbose
ccs son /plan "add feature"
ccs default --model claude-sonnet-4

Custom Config Location

export CCS_CONFIG=~/my-custom-config.json
ccs glm

Use Cases

Real Workflow: Task-Based Model Selection

Scenario: Building a new payment integration feature

# Step 1: Architecture & Planning (needs Claude's intelligence)
ccs son
/plan "Design payment integration with Stripe, handle webhooks, errors, retries"
# → Claude Sonnet 4.5 thinks deeply about edge cases, security, architecture

# Step 2: Implementation (straightforward coding, use GLM)
ccs glm
/code "implement the payment webhook handler from the plan"
# → GLM 4.6 writes the code efficiently, saves Claude usage

# Step 3: Code Review (needs deep analysis)
ccs son
/review "check the payment handler for security issues"
# → Claude Sonnet 4.5 catches subtle vulnerabilities

# Step 4: Bug Fixes (simple)
ccs glm
/fix "update error message formatting"
# → GLM 4.6 handles routine fixes

Result: Best model for each task, lower costs, better quality.

Real Workflow: Rate Limit Management

# Working on complex refactoring with Claude
ccs son
/plan "refactor authentication system"

# Claude hits rate limit mid-task
# → Error: Rate limit exceeded

# Switch to GLM instantly
ccs glm
# Continue working without interruption

# Rate limit resets? Switch back
ccs son

Configuration Examples

Standard setup (Claude sub + GLM):

{
  "profiles": {
    "glm": "~/.ccs/glm.settings.json",
    "sonnet": "~/.ccs/sonnet.settings.json",
    "default": "~/.claude/settings.json"
  }
}

Advanced setup (multiple providers):

{
  "profiles": {
    "sonnet": "~/.ccs/sonnet.settings.json",
    "glm": "~/.ccs/glm.settings.json",
    "haiku": "~/.ccs/haiku.settings.json",
    "default": "~/.claude/settings.json"
  }
}

How It Works

1. Reads profile name (defaults to "default" if omitted)
2. Looks up settings file path in ~/.ccs/config.json
3. Executes claude --settings <path> [remaining-args]

No magic. No file modification. Pure delegation.

Requirements

macOS / Linux

• bash 3.2+
• jq (JSON processor)
• Claude CLI

Windows

• PowerShell 5.1+ (pre-installed on Windows 10+)
• Claude CLI

Installing jq (macOS / Linux only)

# macOS
brew install jq

# Ubuntu/Debian
sudo apt install jq

# Fedora
sudo dnf install jq

# Arch
sudo pacman -S jq

Note: Windows version uses PowerShell's built-in JSON support - no jq required.

Troubleshooting

Windows-Specific Issues

PowerShell Execution Policy

If you see "cannot be loaded because running scripts is disabled":

# Check current policy
Get-ExecutionPolicy

# Allow current user to run scripts (recommended)
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

# Or run with bypass (one-time)
powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.ccs\ccs.ps1" glm

PATH not updated (Windows)

If ccs command not found after installation:

1. Restart your terminal
2. Or manually add to PATH:
   • Open "Edit environment variables for your account"
   • Add %USERPROFILE%\.ccs to User PATH
   • Restart terminal

Claude CLI not found (Windows)

# Check Claude CLI
where.exe claude

# If missing, install from Claude docs

Installation Issues

BASH_SOURCE unbound variable error

This error occurs when running the installer in some shells or environments.

Fixed in latest version: The installer now handles both piped execution (curl | bash) and direct execution (./install.sh).

Solution: Upgrade to the latest version:

curl -fsSL https://raw.githubusercontent.com/kaitranntt/ccs/main/install.sh | bash

Git worktree not detected

If installing from a git worktree or submodule, older versions may fail to detect the git repository.

Fixed in latest version: The installer now detects both .git directory (standard clone) and .git file (worktree/submodule).

Solution: Upgrade to the latest version or use the curl installation method.

Configuration Issues

Profile not found

Error: Profile 'foo' not found in ~/.ccs/config.json

Fix: Add profile to ~/.ccs/config.json:

{
  "profiles": {
    "foo": "~/.ccs/foo.settings.json"
  }
}

Settings file missing

Error: Settings file not found: ~/.ccs/foo.settings.json

Fix: Create settings file or fix path in config.

jq not installed

Error: jq is required but not installed

Fix: Install jq (see Requirements).

Note: The installer creates basic templates even without jq, but enhanced features require jq.

Environment Issues

PATH not set

⚠️  Warning: ~/.local/bin is not in PATH

Fix: Add to ~/.bashrc or ~/.zshrc:

export PATH="$HOME/.local/bin:$PATH"

Then source ~/.bashrc or restart shell.

Default profile missing

Error: Profile 'default' not found in ~/.ccs/config.json

Fix: Add "default" profile or always specify profile name:

{
  "profiles": {
    "default": "~/.claude/settings.json"
  }
}

Upgrade Issues

API keys lost after upgrade

Not a problem: The installer preserves existing API keys when upgrading. If you're using GLM, your API key is automatically preserved and the profile is enhanced with new default model variables.

Verification: Check ~/.ccs/glm.settings.json - your ANTHROPIC_AUTH_TOKEN should still be present.

Uninstallation

macOS / Linux

Using installed command:

ccs-uninstall

One-liner:

# Short URL
curl -fsSL ccs.kaitran.ca/uninstall | bash

# Or direct from GitHub
curl -fsSL https://raw.githubusercontent.com/kaitranntt/ccs/main/uninstall.sh | bash

Manual:

rm ~/.local/bin/ccs
rm ~/.local/bin/ccs-uninstall
rm -rf ~/.ccs  # If you want to remove all CCS files

Windows PowerShell

Using installed command:

ccs-uninstall

One-liner:

# Short URL
irm ccs.kaitran.ca/uninstall.ps1 | iex

# Or direct from GitHub
irm https://raw.githubusercontent.com/kaitranntt/ccs/main/uninstall.ps1 | iex

Manual:

# Remove scripts
Remove-Item "$env:USERPROFILE\.ccs\ccs.ps1" -Force
Remove-Item "$env:USERPROFILE\.ccs\uninstall.ps1" -Force

# Remove from PATH
$Path = [Environment]::GetEnvironmentVariable("Path", "User")
$NewPath = ($Path -split ';' | Where-Object { $_ -ne "$env:USERPROFILE\.ccs" }) -join ';'
[Environment]::SetEnvironmentVariable("Path", $NewPath, "User")

# Optional: Remove all CCS files
Remove-Item "$env:USERPROFILE\.ccs" -Recurse -Force

Contributing

PRs welcome! Keep it simple (KISS principle).

Guidelines:

• Maintain bash 3.2+ compatibility (Unix) and PowerShell 5.1+ (Windows)
• No dependencies beyond jq (Unix) or built-in PowerShell (Windows)
• Test on macOS, Linux, and Windows
• Follow existing code style

Philosophy

• YAGNI: No features "just in case"
• KISS: Simple bash, no complexity
• DRY: One source of truth (config)

This tool does ONE thing well: map profile names to settings files.

License

MIT © Kai Tran

Links

• Claude CLI Docs
• Report Issues
• Changelog