/install cc
cc — Claude Code Relay
Operate Claude Code remotely from any OpenClaw channel via tmux.
Continues your existing claude -c sessions — ACP creates new sessions, cc connects to what's already running.
Language: Always reply in the same language the user uses.
Script
{baseDir}/scripts/cc.sh \x3Ccommand> [args...]
Commands
| Command | Action |
|---|---|
/cc on \x3Cproject> |
Start session (claude -c in project dir) |
/cc off [project] |
Stop session |
/cc ? |
Check Claude Code status (running/idle/dead) |
/cc tail [project] [lines] |
Show recent output |
/cc projects |
List available projects |
/cc status |
List active sessions |
/cc config root \x3Cpath> |
Set project root directory |
/cc |
Show help + project list |
/cc \x3Cmessage> |
Send message to Claude Code |
Relay Mode (CRITICAL)
After /cc on \x3Cproject>, you enter relay mode:
- ALL user messages are forwarded to Claude Code — NEVER answer yourself
- Only messages NOT forwarded:
/cc off,/cc ?,/cc tail,/cc status,/cc projects,/cc config - Relay mode ends on
/cc off
You are a transparent pipe. Never interpret, analyze, or answer the user's question yourself.
Starting a Session
- Run:
scripts/cc.sh on \x3Cproject> - Report to user:
✅ Claude Code session started for \x3Cproject> Your messages will now be sent directly to Claude Code. Send /cc off to exit relay mode. - Enter relay mode
Sending Messages (relay flow)
When user sends a message in relay mode:
- Immediately reply: ⏳ (so user knows message was received)
- Forward:
scripts/cc.sh \x3Cproject> "\x3Cuser's message>" - The script returns the incremental output — only content from this reply, not history
- Return output to user (see Output Formatting below)
Stopping a Session
- Run:
scripts/cc.sh off \x3Cproject> - Report to user:
Session ended. You're back to normal chat.
Status Check (/cc ?)
Run: scripts/cc.sh check \x3Cproject>
Report result to user:
- "🟢 Claude Code is running and waiting for input"
- "🔄 Claude Code is processing..."
- "🔴 Claude Code process died — try /cc off then /cc on to restart"
- "⚪ No active session"
/cc (no arguments)
Run scripts/cc.sh projects. Show brief help + project list.
If there's a last-used project (marked with ★), show it first. Keep the response short — just names, no paths.
First-time Setup
When scripts/cc.sh projects outputs SETUP_NEEDED (exit 100):
- Check:
which tmuxandwhich claude— report if missing - Ask user: "Where are your projects? (e.g., ~/projects)"
- Run:
scripts/cc.sh config root \x3Ctheir-answer> - List projects to confirm
Output Formatting
If output ≤ 4000 characters: wrap in one code block and send.
If output > 4000 characters: send a summary of the key output (first meaningful paragraph + last 10 lines), then add: "Full output: send /cc tail to see more"
Always: strip ANSI escape codes (the script handles this automatically).
Requirements
tmuxinstalledclaudeCLI installed (npm i -g @anthropic-ai/claude-code)- Any OpenClaw channel (Telegram, Discord, CLI, etc.)
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install cc - After installation, invoke the skill by name or use
/cc - Provide required inputs per the skill's parameter spec and get structured output
What is Cc?
Claude Code relay via tmux. Operate Claude Code remotely — start sessions, send messages, read output. Use when the user wants to interact with Claude Code f... It is an AI Agent Skill for Claude Code / OpenClaw, with 663 downloads so far.
How do I install Cc?
Run "/install cc" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Cc free?
Yes, Cc is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Cc support?
Cc is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Cc?
It is built and maintained by XING (@artwalker); the current version is v2.1.0.