CC-Connect AI Bridge
Skill by ara.so — Daily 2026 Skills collection.
CC-Connect bridges locally running AI coding agents (Claude Code, Codex, Cursor Agent, Gemini CLI, Qoder CLI, OpenCode, iFlow CLI) to messaging platforms you already use. You can chat with your local agent from Telegram, Feishu, Slack, Discord, DingTalk, WeChat Work, LINE, or QQ — no public IP required for most platforms.
Installation
Via npm (recommended)
Via binary
Build from source (Go 1.22+)
Self-update
Quick AI-assisted Setup
Send this prompt to Claude Code or any AI coding agent — it will install and configure cc-connect automatically:
Configuration
Minimal config.toml — Claude Code + Telegram
Multi-project config
All supported platform types
All supported agent types
Platform-specific configuration
Telegram
Feishu / Lark
Slack
Discord
DingTalk
WeChat Work (WeCom)
Personal WeChat (beta only)
Running cc-connect
Chat Commands (sent in the messaging platform)
Slash command examples (in chat)
Multi-Agent Relay (group chat orchestration)
Bind multiple bots in one group chat so they communicate with each other:
Add both bots to the same Telegram group. Mention them by name and they will pick up and respond to each other's output.
Voice and Multimodal
For platforms that support voice (Telegram, Feishu, DingTalk), enable speech in config:
Send a voice message in Telegram → cc-connect transcribes it → forwards text to the agent → optionally speaks the response back.
For images/screenshots: just attach the image in chat. cc-connect forwards it to multimodal-capable agents.
Cron Scheduling
From chat:
Admin configuration
Admins can use /shell, /dir, and other privileged commands. Non-admins cannot.
Directory structure
Common patterns
Pattern 1: Mobile-first AI development
Install cc-connect on your dev machine, connect it to Telegram. From your phone:
- Send a task description as a message
- Agent runs on your machine
- Streamed response appears in chat
- Reply to continue the conversation
Pattern 2: Team shared AI bot (Slack/Feishu)
One cc-connect instance per project, shared in a team channel. Team members can ask questions, trigger code reviews, or run analyses — all without terminal access.
Pattern 3: Scheduled reports
Pattern 4: Multi-project routing
Run multiple projects in one cc-connect process, each bot handles a different repo or concern.
Troubleshooting
Bot not responding
- Check that
cc-connectis running:ps aux | grep cc-connect - Verify the platform token/credentials in config
- For Telegram: ensure the bot token is valid (
/startin BotFather chat) - For Feishu: check WebSocket connection in Feishu Open Platform console
Agent not found
Set explicit path in config if needed:
Session inherits broken state
Use /continue which forks the session, or start fresh:
Personal WeChat not available
You need the beta build:
Context too long / auto-compress
Enable in config:
Config not found
Default path is ~/.cc-connect/config.toml. Pass explicitly:
Check version
Environment variables reference
Values in config.toml can reference env vars using $VAR_NAME syntax.
Platform setup guides
- Feishu/Lark:
docs/feishu.md - DingTalk:
docs/dingtalk.md - Telegram:
docs/telegram.md - Slack:
docs/slack.md - Discord:
docs/discord.md - WeChat Work:
docs/wecom.md - Personal WeChat (beta):
docs/weixin.md - QQ / QQ Bot:
docs/qq.md


