@kaitranntt/ccs 3.4.5 → 3.5.0

package/README.md

@@ -1,12 +1,12 @@
-# CCS - Claude Code Switch
-
 <div align="center">
 
+# CCS - Claude Code Switch
+
 ![CCS Logo](docs/assets/ccs-logo-medium.png)
 
-**One command, zero downtime, multiple accounts**
+### One command, zero downtime, multiple accounts
 
-Switch between multiple Claude accounts, GLM, and Kimi instantly.<br>
+**Switch between multiple Claude accounts, GLM, and Kimi instantly.**<br>
 Stop hitting rate limits. Keep working continuously.
 
 
@@ -19,27 +19,20 @@ Stop hitting rate limits. Keep working continuously.
 
 </div>
 
----
-
-## 🚀 Quick Start
+<br>
 
-### 🔑 Prerequisites
-
-**Before installing CCS, make sure you're logged into Claude CLI with your subscription account:**
-```bash
-claude /login
-```
+## Quick Start
 
 ### Installation
 
-#### Option 1: npm Package (Recommended)
+**npm Package (Recommended)**
 
 **macOS / Linux / Windows**
 ```bash
 npm install -g @kaitranntt/ccs
 ```
 
-All major package managers are supported:
+**All major package managers are supported:**
 
 ```bash
 # yarn
@@ -52,7 +45,10 @@ pnpm add -g @kaitranntt/ccs
 bun add -g @kaitranntt/ccs
 ```
 
-#### Option 2: Direct Install (Traditional)
+<details>
+<summary><strong>Alternative: Direct Install (Traditional)</strong></summary>
+
+<br>
 
 **macOS / Linux**
 ```bash
@@ -64,7 +60,11 @@ curl -fsSL ccs.kaitran.ca/install | bash
 irm ccs.kaitran.ca/install | iex
 ```
 
-> **💡 Performance Tip**: Traditional installs bypass Node.js routing for faster startup, but I prioritize npm updates due to easier deployment automation.
+**Note:** Traditional installs bypass Node.js routing for faster startup, but npm is prioritized for easier deployment automation.
+
+</details>
+
+<br>
 
 ### Configuration (Auto-created)
 
@@ -82,7 +82,10 @@ irm ccs.kaitran.ca/install | iex
 }
 ```
 
-### Custom Claude CLI Path
+<details>
+<summary><h3>Custom Claude CLI Path</h3></summary>
+
+<br>
 
 If Claude CLI is installed in a non-standard location (D drive, custom directory), set `CCS_CLAUDE_PATH`:
 
@@ -91,9 +94,14 @@ export CCS_CLAUDE_PATH="/path/to/claude"              # Unix
 $env:CCS_CLAUDE_PATH = "D:\Tools\Claude\claude.exe"   # Windows
 ```
 
-**See [Troubleshooting Guide](./docs/en/troubleshooting.md#claude-cli-in-non-standard-location) for detailed setup instructions.**
+**See also:** [Troubleshooting Guide](./docs/en/troubleshooting.md#claude-cli-in-non-standard-location) for detailed setup instructions.
+
+</details>
+
+<details>
+<summary><h3>Windows Symlink Support (Developer Mode)</h3></summary>
 
-### Windows Symlink Support (Developer Mode)
+<br>
 
 **Windows users**: Enable Developer Mode for true symlinks (better performance, instant sync):
 
@@ -101,60 +109,175 @@ $env:CCS_CLAUDE_PATH = "D:\Tools\Claude\claude.exe"   # Windows
 2. Enable **Developer Mode**
 3. Reinstall CCS: `npm install -g @kaitranntt/ccs`
 
-**Without Developer Mode**: CCS automatically falls back to copying directories (works but no instant sync across profiles).
+**Warning:** Without Developer Mode, CCS automatically falls back to copying directories (works but no instant sync across profiles).
 
----
+</details>
+
+<br>
 
 ### Your First Switch
 
-> **⚠️ Important**: Before using GLM/GLMT or Kimi profiles, update API keys in settings files:
-> - **GLM**: Edit `~/.ccs/glm.settings.json` and add your GLM API key
-> - **GLMT**: Edit `~/.ccs/glmt.settings.json` and add your Z.AI API key (requires coding plan)
+> [!IMPORTANT]
+> **Before using alternative models, update API keys in settings files:**
+>
+> - **GLM**: Edit `~/.ccs/glm.settings.json` and add your Z.AI Coding Plan API Key
+> - **GLMT**: Edit `~/.ccs/glmt.settings.json` and add your Z.AI Coding Plan API Key
 > - **Kimi**: Edit `~/.ccs/kimi.settings.json` and add your Kimi API key
 
+<br>
+
+**Parallel Workflow: Planning + Execution**
+
 ```bash
-# Default Claude subscription
-ccs "Plan microservices architecture"
+# Terminal 1 - Planning (Claude Sonnet)
+ccs "Plan a REST API with authentication and rate limiting"
+
+# Terminal 2 - Execution (GLM, cost-optimized)
+ccs glm "Implement the user authentication endpoints from the plan"
+```
+
+<details>
+<summary><strong>Thinking Models (Kimi & GLMT)</strong></summary>
 
-# Switch to GLM (cost-optimized)
-ccs glm "Create REST API"
+<br>
 
-# GLM with thinking mode
-ccs glmt "Solve algorithmic problem"
+```bash
+# Kimi - Stable thinking support
+ccs kimi "Design a caching strategy with trade-off analysis"
 
-# Kimi for coding
-ccs kimi "Write integration tests"
+# GLMT - Experimental (see full disclaimer below)
+ccs glmt "Debug complex algorithm with reasoning steps"
 ```
 
----
+**Note:** GLMT is experimental and unstable. See [GLM with Thinking (GLMT)](#glm-with-thinking-glmt) section below for full details.
+
+</details>
+
+<br>
 
 ## The Daily Developer Pain Point
 
-Developers face multiple subscription scenarios daily:
+<div align="center">
+
+### **STOP Switching. START Orchestrating.**
+
+**Session limits shouldn't kill your flow state.**
+</div>
+
+You're deep in implementation. Context loaded. Solution crystallizing.<br>
+Then: 🔴 _"You've reached your usage limit."_
+
+**Momentum gone. Context lost. Productivity crater.**
+
+## **The Solution: Parallel Workflows**
+
+<details>
+<summary><strong>❌ OLD WAY:</strong> Switch When You Hit Limits (Reactive)</summary>
+
+### Your Current Workflow:
+- **2pm:** Building features, in the zone
+- **3pm:** 🔴 Usage limit hit
+- **3:05pm:** Stop work, edit `~/.claude/settings.json`
+- **3:15pm:** Switch accounts, lose context
+- **3:30pm:** Try to get back in flow state
+- **4pm:** Finally productive again
+
+- **Result:** 1 hour lost, momentum destroyed, frustration builds
+
+</details>
+
+<details open>
+<summary><strong>✨ NEW WAY:</strong> Run Parallel From Start (Proactive) - <strong>RECOMMENDED</strong></summary>
+
+### Your New Workflow:
+- **2pm:** **Terminal 1:** `ccs "Plan the API architecture"` → Strategic thinking (Claude Pro)
+- **2pm:** **Terminal 2:** `ccs glm "Implement the endpoints"` → Code execution (GLM)
+- **3pm:** Still shipping, no interruptions
+- **4pm:** Flow state achieved, productivity spiking
+- **5pm:** Features shipped, context maintained
+
+- **Result:** Zero downtime, continuous productivity, less frustration
+
+### 💰 **The Value Proposition:**
+- **Setup:** Your existing Claude Pro + GLM Lite (cost-effective add-on)
+- **Value:** Save 1 hour/day × 20 workdays = 20 hours/month recovered
+- **ROI:** Your development time is worth more than the setup cost
+- **Reality:** Shipping faster than the overhead
+
+</details>
+
+## Choose Your Path
+
+<details>
+<summary><strong>Budget-Focused:</strong> GLM Only</summary>
+
+- **Best for:** Cost-conscious development, basic code generation
+- **Usage:** Just use `ccs glm` directly for cost-effective AI assistance
+- **Reality:** No Claude access, but capable for many coding tasks
+- **Setup:** GLM API key only, very affordable
+
+</details>
 
-1. **Account Separation**: Company Claude account vs personal Claude → you must manually switch contexts to keep work and personal separate
-2. **Rate Limits Hit**: Claude stops mid-project → you manually edit `~/.claude/settings.json`
-3. **Cost Management**: 2-3 Pro subscriptions ($20/month each) vs Claude Max at 5x cost ($100/month) → Pro tier is the practical ceiling for most developers
-4. **Model Choice**: Different tasks benefit from different model strengths → manual switching
+<details open>
+<summary><strong>✨ Recommended for Daily Development:</strong> 1 Claude Pro + 1 GLM Lite</summary>
 
-Manual context switching breaks your workflow. **CCS manages it seamlessly**.
+- **Best for:** Daily code delivery, serious development work
+- **Usage:** `ccs` for planning + `ccs glm` for execution (parallel workflow)
+- **Reality:** Perfect balance of capability and cost for most developers
+- **Value:** Never hit session limits, continuous productivity
+
+</details>
+
+<details>
+<summary><strong>Power User:</strong> Multiple Claude Pro + GLM Pro</summary>
+
+- **Best for:** Heavy workloads, concurrent projects, solo dev
+- **Unlocks:** Never drain session or weekly limits
+- **Workflow:** 3+ terminals running specialized tasks simultaneously
+
+</details>
+
+<details>
+<summary><strong>Privacy-Focused:</strong> Work/Personal Isolation</summary>
+
+- **When needed:** Strict separation of work and personal AI contexts
+- **Setup:** `ccs auth create work` + `ccs auth create personal`
+- **Note:** Advanced feature - most users don't need this
+
+</details>
+
+---
 
 ## Why CCS Instead of Manual Switching?
 
 <div align="center">
 
-| Feature | Benefit |
-|---------|---------|
-| **Account Isolation** | Keep work separate from personal |
-| **Cost Optimization** | 2-3 Pro accounts vs Max at 5x cost |
-| **Instant Switching** | One command, no file editing |
-| **Zero Downtime** | Never interrupt workflow |
-| **Rate Limit Management** | Switch accounts when limits hit |
-| **Cross-Platform** | macOS, Linux, Windows |
+**CCS isn't about "switching when you hit limits at 3pm."**
+
+## **It's about running in parallel from the start.**
 
 </div>
 
----
+### The Core Difference
+
+| **Manual Switching** | **CCS Orchestration** |
+|:---|:---|
+| 🔴 Hit limits → Stop work → Edit config files → Restart | ✅ Multiple terminals running different models from the start |
+| 😰 Context loss and flow state interruption | 😌 Continuous productivity with preserved context |
+| 📝 Sequential task handling | ⚡ Parallel workflows (planning + execution simultaneously) |
+| 🛠️ Reactive problem solving when blocked | 🎯 Proactive workflow design prevents blocks |
+
+### What CCS Gives You
+
+- **Zero Context Switching**: Keep your flow state without interruption
+- **Parallel Productivity**: Strategic planning in one terminal, code execution in another
+- **Instant Account Management**: One command switches, no config file editing
+- **Work-Life Separation**: Isolate contexts without logging out
+- **Cross-Platform Consistency**: Same smooth experience on macOS, Linux, Windows
+
+**Manual context switching breaks workflow. CCS orchestrates seamlessly.**
+
+<br>
 
 ## Architecture
 
@@ -170,9 +293,9 @@ Manual context switching breaks your workflow. **CCS manages it seamlessly**.
 
 ### Shared Data (v3.1)
 
-Commands and skills symlinked from `~/.ccs/shared/` - no duplication across profiles.
+Commands and skills symlinked from `~/.ccs/shared/` - **no duplication across profiles**.
 
-```
+```plaintext
 ~/.ccs/
 ├── shared/                  # Shared across all profiles
 │   ├── agents/
@@ -184,24 +307,77 @@ Commands and skills symlinked from `~/.ccs/shared/` - no duplication across prof
 │       ├── commands@ → shared/commands/
 │       ├── skills@ → shared/skills/
 │       ├── settings.json    # API keys, credentials
-│       └── sessions/        # Conversation history
+│       ├── sessions/        # Conversation history
 │       └── ...
 ```
 
-**Shared**: commands/, skills/, agents/
-**Profile-specific**: settings.json, sessions/, todolists/, logs/
+| Type | Files |
+|:-----|:------|
+| **Shared** | `commands/`, `skills/`, `agents/` |
+| **Profile-specific** | `settings.json`, `sessions/`, `todolists/`, `logs/` |
 
-**[i] Windows**: Copies dirs if symlinks unavailable (enable Developer Mode for true symlinks)
+> [!NOTE]
+> **Windows**: Copies directories if symlinks unavailable (enable Developer Mode for true symlinks)
 
----
+<br>
+
+## Usage Examples
+
+### Basic Switching
+
+```bash
+ccs              # Claude subscription (default)
+ccs glm          # GLM (cost-optimized)
+ccs kimi         # Kimi (with thinking support)
+```
+
+### Multi-Account Setup
+
+```bash
+# Create accounts
+ccs auth create work
+ccs auth create personal
+```
+
+**Run concurrently in separate terminals:**
+
+```bash
+# Terminal 1 - Work
+ccs work "implement feature"
+
+# Terminal 2 - Personal (concurrent)
+ccs personal "review code"
+```
+
+### Help & Version
+
+```bash
+ccs --version    # Show version
+ccs --help       # Show all commands and options
+```
+
+<br>
 
 ## GLM with Thinking (GLMT)
 
-> **[!] Important**: GLMT requires npm installation (`npm install -g @kaitranntt/ccs`). Not available in native shell versions (requires Node.js HTTP server).
+> [!CAUTION]
+> ### NOT PRODUCTION READY - EXPERIMENTAL FEATURE
+>
+> **GLMT is experimental and requires extensive debugging**:
+> - Streaming and tool support still under active development
+> - May experience unexpected errors, timeouts, or incomplete responses
+> - Requires frequent debugging and manual intervention
+> - **Not recommended for critical workflows or production use**
+>
+> **Alternative for GLM Thinking**: Consider going through the **CCR hustle** with the **Transformer of Bedolla** ([ZaiTransformer](https://github.com/Bedolla/ZaiTransformer/)) for a more stable implementation.
+
+> [!IMPORTANT]
+> GLMT requires npm installation (`npm install -g @kaitranntt/ccs`). Not available in native shell versions (requires Node.js HTTP server).
 
-### Acknowledgments: The Foundation That Made GLMT Possible
+<br>
 
-> **[i] Pioneering Work by [@Bedolla](https://github.com/Bedolla)**
+> [!NOTE]
+> ### Acknowledgments: The Foundation That Made GLMT Possible
 >
 > **CCS's GLMT implementation owes its existence to the groundbreaking work of [@Bedolla](https://github.com/Bedolla)**, who created [ZaiTransformer](https://github.com/Bedolla/ZaiTransformer/) - the **first integration** to bridge [Claude Code Router (CCR)](https://github.com/musistudio/claude-code-router) with Z.AI's reasoning capabilities.
 >
@@ -215,81 +391,122 @@ Commands and skills symlinked from `~/.ccs/shared/` - no duplication across prof
 >
 > **Recognition**: If you benefit from GLMT's thinking capabilities, you're benefiting from Bedolla's vision and engineering. Please consider starring [ZaiTransformer](https://github.com/Bedolla/ZaiTransformer/) to support pioneering work in the Claude Code ecosystem.
 
----
+<br>
+
+<details>
+<summary><h3>GLM vs GLMT Comparison</h3></summary>
+
+<br>
 
-### GLM vs GLMT
+<div align="center">
 
 | Feature | GLM (`ccs glm`) | GLMT (`ccs glmt`) |
-|---------|-----------------|-------------------|
+|:--------|:----------------|:------------------|
 | **Endpoint** | Anthropic-compatible | OpenAI-compatible |
-| **Thinking** | No | Yes (reasoning_content) |
-| **Tool Support** | Basic | **Full (v3.5+)** |
-| **MCP Tools** | Limited | **Working (v3.5+)** |
-| **Streaming** | Yes | **Yes (v3.4+)** |
-| **TTFB** | <500ms | <500ms (streaming), 2-10s (buffered) |
-| **Use Case** | Fast responses | Complex reasoning + tools |
+| **Thinking** | No | Experimental (`reasoning_content`) |
+| **Tool Support** | Basic | **Unstable (v3.5+)** |
+| **MCP Tools** | Limited | **Buggy (v3.5+)** |
+| **Streaming** | Stable | **Experimental (v3.4+)** |
+| **TTFB** | <500ms | <500ms (sometimes), 2-10s+ (often) |
+| **Use Case** | Reliable work | **Debugging experiments only** |
+
+</div>
+
+</details>
+
+<details>
+<summary><h3>Tool Support (v3.5) - EXPERIMENTAL</h3></summary>
+
+<br>
 
-### Tool Support (v3.5)
+**GLMT attempts MCP tools and function calling:**
 
-**GLMT now fully supports MCP tools and function calling**:
+- **Bidirectional Transformation**: Anthropic tools ↔ OpenAI format (unstable)
+- **MCP Integration**: MCP tools sometimes execute (often output XML garbage)
+- **Streaming Tool Calls**: Real-time tool calls (when not crashing)
+- **Backward Compatible**: May break existing thinking support
+- **Configuration Required**: Frequent manual debugging needed
 
-- **Bidirectional Transformation**: Anthropic tools ↔ OpenAI function calling
-- **MCP Integration**: MCP tools execute correctly (no XML tag output)
-- **Streaming Tool Calls**: Real-time tool calls with input_json deltas
-- **Backward Compatible**: Works seamlessly with existing thinking support
-- **No Configuration**: Tool support works automatically
+</details>
 
-### Streaming Support (v3.4)
+<details>
+<summary><h3>Streaming Support (v3.4) - OFTEN FAILS</h3></summary>
 
-**GLMT now supports real-time streaming** with incremental reasoning content delivery.
+<br>
 
-- **Default**: Streaming enabled (TTFB <500ms)
-- **Disable**: Set `CCS_GLMT_STREAMING=disabled` for buffered mode
-- **Force**: Set `CCS_GLMT_STREAMING=force` to override client preferences
-- **Thinking parameter**: Claude CLI `thinking` parameter support
-  - Respects `thinking.type` and `budget_tokens`
-  - Precedence: CLI parameter > message tags > default
+**GLMT attempts real-time streaming** with incremental reasoning content delivery:
 
-**Confirmed working**: Z.AI (1498 reasoning chunks tested, tool calls verified)
+- **Default**: Streaming enabled (TTFB <500ms when it works)
+- **Auto-fallback**: Frequently switches to buffered mode due to errors
+- **Thinking parameter**: Claude CLI `thinking` parameter sometimes works
+  - May ignore `thinking.type` and `budget_tokens`
+  - Precedence: CLI parameter > message tags > default (when not broken)
 
-### How It Works
+**Status**: Z.AI (tested, tool calls frequently break, requires constant debugging)
 
-1. CCS spawns embedded HTTP proxy on localhost
-2. Proxy converts Anthropic format → OpenAI format (streaming or buffered)
-3. Transforms Anthropic tools → OpenAI function calling format
-4. Forwards to Z.AI with reasoning parameters and tools
-5. Converts `reasoning_content` → thinking blocks (incremental or complete)
-6. Converts OpenAI `tool_calls` → Anthropic tool_use blocks
-7. Thinking and tool calls appear in Claude Code UI in real-time
+</details>
 
-### Control Tags
+<details>
+<summary><h3>How It Works (When It Works)</h3></summary>
 
+<br>
+
+1. CCS spawns embedded HTTP proxy on localhost (if not crashing)
+2. Proxy attempts to convert Anthropic format → OpenAI format (often fails)
+3. Tries to transform Anthropic tools → OpenAI function calling format (buggy)
+4. Forwards to Z.AI with reasoning parameters and tools (when not timing out)
+5. Attempts to convert `reasoning_content` → thinking blocks (partial or broken)
+6. Attempts to convert OpenAI `tool_calls` → Anthropic `tool_use` blocks (XML garbage common)
+7. Thinking and tool calls sometimes appear in Claude Code UI (when not broken)
+
+</details>
+
+<details>
+<summary><h3>Control Tags & Keywords</h3></summary>
+
+<br>
+
+**Control Tags**:
 - `<Thinking:On|Off>` - Enable/disable reasoning blocks (default: On)
 - `<Effort:Low|Medium|High>` - Control reasoning depth (deprecated - Z.AI only supports binary thinking)
 
-### Environment Variables
+**Thinking Keywords** (inconsistent activation):
+- `think` - Sometimes enables reasoning (low effort)
+- `think hard` - Sometimes enables reasoning (medium effort)
+- `think harder` - Sometimes enables reasoning (high effort)
+- `ultrathink` - Attempts maximum reasoning depth (often breaks)
+
+</details>
 
-**GLMT-specific**:
-- `CCS_GLMT_FORCE_ENGLISH=true` - Force English output (default: true)
-- `CCS_GLMT_THINKING_BUDGET=8192` - Control thinking on/off based on task type
-  - 0 or "unlimited": Always enable thinking
-  - 1-2048: Disable thinking (fast execution)
-  - 2049-8192: Enable for reasoning tasks only (default)
-  - >8192: Always enable thinking
-- `CCS_GLMT_STREAMING=disabled` - Force buffered mode
-- `CCS_GLMT_STREAMING=force` - Force streaming (override client)
+<details>
+<summary><h3>Environment Variables</h3></summary>
+
+<br>
+
+**GLMT features** (all experimental):
+- Forced English output enforcement (sometimes works)
+- Random thinking mode activation (unpredictable)
+- Attempted streaming with frequent fallback to buffered mode
 
 **General**:
 - `CCS_DEBUG_LOG=1` - Enable debug file logging
 - `CCS_CLAUDE_PATH=/path/to/claude` - Custom Claude CLI path
 
-### API Key Setup
+</details>
+
+<details>
+<summary><h3>API Key Setup</h3></summary>
+
+<br>
 
 ```bash
 # Edit GLMT settings
 nano ~/.ccs/glmt.settings.json
+```
+
+Set Z.AI API key (requires coding plan):
 
-# Set Z.AI API key (requires coding plan)
+```json
 {
   "env": {
     "ANTHROPIC_AUTH_TOKEN": "your-z-ai-api-key"
@@ -297,15 +514,28 @@ nano ~/.ccs/glmt.settings.json
 }
 ```
 
-### Security Limits
+</details>
+
+<details>
+<summary><h3>Security Limits (DoS Protection)</h3></summary>
+
+<br>
+
+**v3.4 Protection Limits**:
+
+| Limit | Value | Purpose |
+|:------|:------|:--------|
+| **SSE buffer** | 1MB max per event | Prevent buffer overflow |
+| **Content buffer** | 10MB max per block | Limit thinking/text blocks |
+| **Content blocks** | 100 max per message | Prevent DoS attacks |
+| **Request timeout** | 120s | Both streaming and buffered |
+
+</details>
 
-**DoS protection** (v3.4):
-- SSE buffer: 1MB max per event
-- Content buffer: 10MB max per block (thinking/text)
-- Content blocks: 100 max per message
-- Request timeout: 120s (both streaming and buffered)
+<details>
+<summary><h3>Debugging</h3></summary>
 
-### Debugging
+<br>
 
 **Enable verbose logging**:
 ```bash
@@ -319,10 +549,10 @@ ccs glmt --verbose "your prompt"
 # Logs: ~/.ccs/logs/
 ```
 
-**Check streaming mode**:
+**GLMT debugging**:
 ```bash
-# Disable streaming for debugging
-CCS_GLMT_STREAMING=disabled ccs glmt "test"
+# Verbose logging shows streaming status and reasoning details
+ccs glmt --verbose "test"
 ```
 
 **Check reasoning content**:
@@ -330,87 +560,53 @@ CCS_GLMT_STREAMING=disabled ccs glmt "test"
 cat ~/.ccs/logs/*response-openai.json | jq '.choices[0].message.reasoning_content'
 ```
 
-**If absent**: Z.AI API issue (verify key, account status)
-**If present**: Transformation issue (check response-anthropic.json)
+**Troubleshooting**:
+- **If absent**: Z.AI API issue (verify key, account status)
+- **If present**: Transformation issue (check `response-anthropic.json`)
 
----
+</details>
 
-## Usage Examples
+<br>
 
-### Basic Switching
-```bash
-ccs              # Claude subscription (default)
-ccs glm          # GLM (no thinking)
-ccs glmt         # GLM with thinking
-ccs kimi         # Kimi for Coding
-ccs --version    # Show version
-```
-
-### Multi-Account Setup
-```bash
-# Create accounts
-ccs auth create work
-ccs auth create personal
-
-# Terminal 1
-ccs work "implement feature"
+## Uninstall
 
-# Terminal 2 (concurrent)
-ccs personal "review code"
-```
+<details>
+<summary><h3>Package Managers</h3></summary>
 
-### Custom Claude CLI Path
+<br>
 
-Non-standard installation location:
 ```bash
-export CCS_CLAUDE_PATH="/path/to/claude"              # Unix
-$env:CCS_CLAUDE_PATH = "D:\Tools\Claude\claude.exe"   # Windows
-```
-
-See [Troubleshooting Guide](./docs/en/troubleshooting.md#claude-cli-in-non-standard-location)
-
----
+# npm
+npm uninstall -g @kaitranntt/ccs
 
-## Configuration
+# yarn
+yarn global remove @kaitranntt/ccs
 
-Auto-created during installation via npm postinstall script.
+# pnpm
+pnpm remove -g @kaitranntt/ccs
 
-**~/.ccs/config.json**:
-```json
-{
-  "profiles": {
-    "glm": "~/.ccs/glm.settings.json",
-    "glmt": "~/.ccs/glmt.settings.json",
-    "kimi": "~/.ccs/kimi.settings.json",
-    "default": "~/.claude/settings.json"
-  }
-}
+# bun
+bun remove -g @kaitranntt/ccs
 ```
 
-Complete guide: [docs/en/configuration.md](./docs/en/configuration.md)
+</details>
 
----
+<details>
+<summary><h3>Official Uninstaller</h3></summary>
 
-## Uninstall
+<br>
 
-**Package Managers**
-```bash
-npm uninstall -g @kaitranntt/ccs
-yarn global remove @kaitranntt/ccs
-pnpm remove -g @kaitranntt/ccs
-bun remove -g @kaitranntt/ccs
-```
-
-**Official Uninstaller**
 ```bash
 # macOS / Linux
 curl -fsSL ccs.kaitran.ca/uninstall | bash
 
-# Windows
+# Windows PowerShell
 irm ccs.kaitran.ca/uninstall | iex
 ```
 
----
+</details>
+
+<br>
 
 ## 🎯 Philosophy
 
@@ -418,8 +614,6 @@ irm ccs.kaitran.ca/uninstall | iex
 - **KISS**: Simple bash, no complexity
 - **DRY**: One source of truth (config)
 
----
-
 ## 📖 Documentation
 
 **Complete documentation in [docs/](./docs/)**:
@@ -431,19 +625,23 @@ irm ccs.kaitran.ca/uninstall | iex
 - [Troubleshooting](./docs/en/troubleshooting.md)
 - [Contributing](./CONTRIBUTING.md)
 
----
-
 ## 🤝 Contributing
 
 We welcome contributions! Please see our [Contributing Guide](./CONTRIBUTING.md) for details.
 
----
 
-## 📄 License
+## Star History
 
-CCS is licensed under the [MIT License](LICENSE).
+<div align="center">
 
----
+<img src="https://api.star-history.com/svg?repos=kaitranntt/ccs&type=timeline&logscale&legend=top-left" alt="Star History Chart" width="800">
+
+</div>
+
+
+## License
+
+CCS is licensed under the [MIT License](LICENSE).
 
 <div align="center">