Install and configure cc-connect to connect personal WeChat (个人微信) with Claude Code as an AI assistant. This skill covers the full setup workflow on Windows: downloading cc-connect, binding WeChat via ilink protocol, configuring config.toml, registering as a Windows service with NSSM for persistent background operation, and RDP-specific fixes. Triggered by requests like "install cc-connect", "connect WeChat to Claude Code", "微信接入 Claude", "cc-connect 安装", "微信 AI 助手 setup".
Resources
4Install
npx skillscat add bj2020wang/cc-connect-wechat Install via the SkillsCat registry.
cc-connect WeChat Setup
Overview
This skill enables connecting personal WeChat (个人微信) to Claude Code via cc-connect,
allowing users to chat with Claude AI directly from their phone's WeChat app. The full
workflow covers installation, WeChat binding, configuration, and Windows service registration
for persistent background operation (survives RDP disconnection and server restarts).
Prerequisites
- Windows 10/11 or Windows Server (RDP environments supported)
- Node.js installed (for Claude Code)
- Claude Code installed (
npm install -g @anthropic-ai/claude-code) - PowerShell with administrator privileges
- Python 3.x available on the system (for download scripts)
Workflow
Step 1: Verify Claude Code Installation
Verify Claude Code is installed and accessible:
claude --version
# Expected: 2.x.x (Claude Code)If not installed, run: npm install -g @anthropic-ai/claude-code
If claude is not found in PATH, locate it manually:
where.exe claude
# Typical path: C:\Users\<username>\AppData\Roaming\npm\claudeRecord the npm global directory for later use in service configuration.
Step 2: Download and Install cc-connect
Option A: Direct browser download
Download from: https://github.com/chenhg5/cc-connect/releases
Look for the latest cc-connect-vX.X.X-windows-amd64.zip file.
Option B: Python download script
Run the bundled download script:
python scripts/download_cc_connect.pyThe script downloads to the system temp directory and prints the file path.
Install:
# Create install directory
New-Item -ItemType Directory -Force -Path "C:\Program Files\cc-connect" | Out-Null
# Extract (replace <download-path> with actual path)
Expand-Archive -Path "<download-path>\cc-connect-vX.X.X-windows-amd64.zip" `
-DestinationPath "C:\Program Files\cc-connect" -Force
# Rename to short name
$exe = Get-ChildItem "C:\Program Files\cc-connect\cc-connect-v*-windows-amd64.exe" | Select-Object -First 1
Copy-Item $exe.FullName "C:\Program Files\cc-connect\cc-connect.exe" -Force
# Add to PATH
[Environment]::SetEnvironmentVariable(
"PATH",
[Environment]::GetEnvironmentVariable("PATH", "User") + ";C:\Program Files\cc-connect",
"User"
)
# Verify
& "C:\Program Files\cc-connect\cc-connect.exe" --versionStep 3: Initialize Config and Bind WeChat
# Initialize default config (creates ~/.cc-connect/config.toml)
& "C:\Program Files\cc-connect\cc-connect.exe"
# Press Ctrl+C after it creates the config
# Bind personal WeChat via ilink protocol
& "C:\Program Files\cc-connect\cc-connect.exe" weixin setupThe weixin setup command displays a QR code in the terminal. Scan it with the phone's
WeChat app to authenticate. On success, the ilink token is automatically written toconfig.toml.
Step 4: Configure config.toml
Edit the config file:
notepad "$env:USERPROFILE\.cc-connect\config.toml"Use references/config_template.toml as a reference. Key changes required:
Set
work_dirto a real Windows path (use double backslashes):work_dir = "C:\\Users\\<username>"Remove or comment out the Feishu platform (if not using it) to avoid error spam.
Add
allow_fromto the weixin platform options to restrict access:allow_from = "<your-wechat-id>@im.wechat"To find the WeChat ID: send a message to the bot, then check cc-connect logs for
user=<id>@im.wechat.Add
admin_fromto enable privileged commands (/shell, /restart, etc.):admin_from = "<your-wechat-id>@im.wechat"
Step 5: Test in Foreground Mode
Before setting up the service, test that everything works:
& "C:\Program Files\cc-connect\cc-connect.exe"Send a message from WeChat. If Claude responds, the setup is correct. Press Ctrl+C to stop.
Critical: Never run multiple cc-connect instances simultaneously. They will conflict
on the .config.toml.lock file.
Step 6: Register as Windows Service (Recommended)
For persistent background operation (survives RDP disconnection, auto-restart on crash,
auto-start on boot), register cc-connect as a Windows service using NSSM.
Run the bundled service setup script in an elevated PowerShell:
& "scripts/setup_ccconnect_service.ps1"The script automatically:
- Stops any running cc-connect process
- Downloads and installs NSSM (from fightroad/nssm GitHub mirror)
- Registers cc-connect as a Windows service (LocalSystem, auto-start)
- Injects the full PATH and user environment variables (critical for LocalSystem to find
claude) - Configures crash auto-restart (5 second delay)
- Starts the service and verifies
Key pitfall: LocalSystem account does not have the user's PATH. WithoutAppEnvironmentExtra injection, the service starts but immediately crashes because it
cannot find the claude command. The script handles this, but for manual setup:
$nssm = "C:\Program Files\nssm\nssm.exe"
& $nssm set cc-connect AppEnvironmentExtra "PATH=$env:PATH" "HOME=$env:USERPROFILE" "USERPROFILE=$env:USERPROFILE" "APPDATA=$env:APPDATA"Step 7: RDP-Specific Fixes (If Applicable)
If the user is on RDP and also wants to use CC Switch (a GUI tool for managing AI provider
configs), WebView2 GPU acceleration causes blank windows. Fix:
[Environment]::SetEnvironmentVariable(
"WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS",
"--disable-gpu",
"User"
)Restart CC Switch after setting this.
Step 8: Verify Service Operation
# Check service status
Get-Service cc-connect | Select-Object Name, Status, StartType
# Check logs
Get-Content "$env:USERPROFILE\.cc-connect\service-stderr.log" -Tail 30
# Send a WeChat message and verify responseService Management Commands
| Command | Description |
|---|---|
net start cc-connect |
Start service |
net stop cc-connect |
Stop service |
net stop cc-connect; net start cc-connect |
Restart service |
Get-Service cc-connect |
Check status |
Get-Content ~\.cc-connect\service-stderr.log -Tail 50 |
View recent logs |
Troubleshooting
See references/troubleshooting.md for detailed solutions to common issues:
- Service status is "Paused" (LocalSystem cannot find claude)
- WeChat shows "暂无法连接" (process died)
- WeChat shows "启动 AGENT 会话失败" (work_dir path issue)
- RDP disconnection kills the process
- Multiple instance lock conflict
- NSSM download failures (nssm.cc 503)
Resources
- scripts/download_cc_connect.py — Python script to download cc-connect zip from GitHub
- scripts/setup_ccconnect_service.ps1 — PowerShell script to register cc-connect as a Windows service via NSSM
- references/troubleshooting.md — Detailed troubleshooting guide for common issues
- references/config_template.toml — Example config.toml with WeChat + allow_from configuration