Skip to main content

Installation

Cross-Platform Installation

npm install -g @kaitranntt/ccs

Benefits

  • ✅ Cross-platform compatibility
  • ✅ Automatic PATH configuration
  • ✅ Auto-creates config files via postinstall script
  • ✅ Easy updates: npm update -g @kaitranntt/ccs
  • ✅ Clean uninstall: npm uninstall -g @kaitranntt/ccs
  • ✅ Version pinning support
  1. npm downloads and installs the package
  2. Postinstall script creates ~/.ccs/config.json and ~/.ccs/glm.settings.json
  3. npm creates ccs command in your PATH
If you use npm install --ignore-scripts, config files won’t be created. Run without that flag or use npm install -g @kaitranntt/ccs --force.

What Gets Installed

Configuration Directory (~/.ccs/):
~/.ccs/
├── config.json             # Profile configuration
├── glm.settings.json       # GLM profile
├── instances/              # Account-based profile instances
├── cliproxy/               # OAuth provider auth tokens
└── shared/                 # Shared commands/skills/agents

Requirements

macOS / Linux

Windows

  • PowerShell 5.1+ (pre-installed on Windows 10+)
  • Node.js 14+
  • Claude CLI

Windows Claude Detection

Available since v7.36.0 - Enhanced Windows Claude CLI detection with fallback paths.
CCS automatically detects Claude CLI installation on Windows: Detection Order:
  1. Windows native installer (AppData)
  2. Local bin fallback paths
  3. npm global installation
  4. Environment variable override
Native Installer Paths:
%USERPROFILE%\.local\bin\claude.exe
%APPDATA%\npm\claude.cmd
Fallback Paths:
%USERPROFILE%\.local\bin\claude.exe
C:\Users\{username}\.local\bin\claude.exe
CCS expands ~ to full user profile path for compatibility. Manual Override: If detection fails, set environment variable:
$env:CCS_CLAUDE_PATH = "C:\custom\path\to\Claude.exe"

Upgrading

# npm (recommended)
npm update -g @kaitranntt/ccs

# Or force reinstall
ccs update --force

Uninstalling

npm uninstall -g @kaitranntt/ccs
This removes the CCS command but preserves your ~/.ccs/ configuration directory.