CCS - Claude Code Switch

One command, zero downtime, right model for each task Switch between Claude Sonnet 4.5 and GLM 4.6 instantly. Stop hitting rate limits. Start optimizing costs. Languages: English | Tiếng Việt

---

🚀 Quick Start

Primary Installation Methods

macOS / Linux

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

Windows PowerShell

irm ccs.kaitran.ca/install | iex

Your First Switch

# Switch to GLM for cost-optimized tasks
ccs glm "Create a simple REST API"

# Switch back to Claude for complex tasks
ccs claude "Review this architecture design"

# Use GLM for all subsequent commands until switched back
ccs glm
ccs "Debug this issue"
ccs "Write unit tests"

Configuration (Auto-created)

~/.ccs/config.json:

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

---

The Daily Developer Pain Point

You have both Claude subscription and GLM Coding Plan. Two scenarios happen every day:

1. Rate Limits Hit: Claude stops mid-project → you manually edit ~/.claude/settings.json
2. Cost Waste: Simple tasks use expensive Claude → GLM would work fine

Manual switching breaks your flow. CCS fixes it instantly.

Why CCS Instead of Manual Switching?

Feature	Benefit	Emotional Value
Instant Switching	One command, no file editing	Confidence, control
Zero Downtime	Never interrupt your workflow	Reliability, consistency
Smart Delegation	Right model for each task automatically	Simplicity, ease
Cost Control	Use expensive models only when needed	Efficiency, savings
Cross-Platform	Works on macOS, Linux, Windows	Flexibility, portability
Reliable	Pure bash/PowerShell, zero dependencies	Trust, peace of mind

The Solution:

ccs           # Use Claude subscription (default)
ccs glm       # Switch to GLM fallback
# Hit rate limit? Switch instantly:
ccs glm       # Continue working with GLM

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

---

🏗️ Architecture Overview

graph LR
    subgraph "User Command"
        CMD[ccs glm]
    end

    subgraph "CCS Processing"
        CONFIG[Read ~/.ccs/config.json]
        LOOKUP[Lookup profile → settings file]
        VALIDATE[Validate file exists]
    end

    subgraph "Claude CLI"
        EXEC[claude --settings <path>]
    end

    subgraph "API Response"
        API[Claude Sub or GLM API]
    end

    CMD --> CONFIG
    CONFIG --> LOOKUP
    LOOKUP --> VALIDATE
    VALIDATE --> EXEC
    EXEC --> API

---

⚡ Features

Instant Profile Switching

• One Command: ccs glm or ccs claude - no config file editing
• Smart Detection: Automatically uses right model for each task
• Persistent: Switch stays active until changed again

Zero Workflow Interruption

• No Downtime: Switching happens instantly between commands
• Context Preservation: Your workflow remains uninterrupted
• Seamless Integration: Works exactly like native Claude CLI

Task Delegation

CCS includes intelligent task delegation via the /ccs meta-command:

Install CCS commands:

ccs --install    # Install /ccs command to Claude CLI

Use task delegation:

# After running ccs --install, you can use:
/ccs glm /plan "add user authentication"
/ccs glm /code "implement auth endpoints"
/ccs glm /ask "explain this error"

Remove when not needed:

ccs --uninstall  # Remove /ccs command from Claude CLI

Benefits:

• ✅ Save tokens by delegating simple tasks to cheaper models
• ✅ Use right model for each task automatically
• ✅ Seamless integration with existing workflows
• ✅ Clean installation and removal when needed

---

💻 Usage Examples

ccs              # Use Claude subscription (default)
ccs glm          # Use GLM fallback
ccs --version    # Show CCS version and install location
ccs --install    # Install CCS commands and skills to ~/.claude/
ccs --uninstall  # Remove CCS commands and skills from ~/.claude/

---

🎯 Philosophy

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

---

🔧 Installation

System Requirements

• Node.js: Not required (pure bash/PowerShell)
• Python: Not required
• Dependencies: Only jq for JSON parsing (Unix systems)
• Claude CLI: Must be installed separately
• API Keys: Valid Claude and GLM API keys

Verification

# Verify installation
ccs --version

# Expected output:
# CCS v2.2.3
# Installed at: ~/.local/bin/ccs (Unix) or %USERPROFILE%\.ccs\ccs.ps1 (Windows)
# Claude CLI: Found at /usr/local/bin/claude

---

🗑️ Uninstall

macOS / Linux:

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

Windows PowerShell:

irm ccs.kaitran.ca/uninstall | iex

---

📖 Documentation

Complete documentation in docs/:

• Installation Guide
• Configuration
• Usage Examples
• Troubleshooting
• Contributing

---

🤝 Contributing

We welcome contributions! Please see our Contributing Guide for details.

---

📄 License

CCS is licensed under the MIT License.

---

Made with ❤️ for developers who hit rate limits too often

⭐ Star this repo | 🐛 Report issues | 📖 Read docs