cc-connect-ai-bridge
Bridge local AI coding agents (Claude Code, Cursor, Gemini CLI, Codex) to messaging platforms (Feishu, Telegram, Slack, Discord, DingTalk, WeChat Work, LINE) without a public IP.
What this skill does
# CC-Connect AI Bridge > Skill by [ara.so](https://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) ```bash # Stable npm install -g cc-connect # Beta (includes personal WeChat / Weixin ilink and other beta features) npm install -g cc-connect@beta ``` ### Via binary ```bash # Linux amd64 curl -L -o cc-connect https://github.com/chenhg5/cc-connect/releases/latest/download/cc-connect-linux-amd64 chmod +x cc-connect sudo mv cc-connect /usr/local/bin/ # macOS arm64 curl -L -o cc-connect https://github.com/chenhg5/cc-connect/releases/latest/download/cc-connect-darwin-arm64 chmod +x cc-connect sudo mv cc-connect /usr/local/bin/ ``` ### Build from source (Go 1.22+) ```bash git clone https://github.com/chenhg5/cc-connect.git cd cc-connect make build # binary appears at ./bin/cc-connect ``` ### Self-update ```bash cc-connect update # stable cc-connect update --pre # beta / pre-release ``` --- ## Quick AI-assisted Setup Send this prompt to Claude Code or any AI coding agent — it will install and configure cc-connect automatically: ``` Follow https://raw.githubusercontent.com/chenhg5/cc-connect/refs/heads/main/INSTALL.md to install and configure cc-connect. ``` --- ## Configuration ```bash mkdir -p ~/.cc-connect cp config.example.toml ~/.cc-connect/config.toml ``` ### Minimal `config.toml` — Claude Code + Telegram ```toml [project.my-project] name = "my-project" work_dir = "/home/user/myproject" data_dir = "/home/user/.cc-connect/data" admin_from = "123456789" # Your Telegram user ID [project.my-project.agent] type = "claude-code" # claude-code | codex | cursor | gemini | qoder | opencode | iflow [project.my-project.platform] type = "telegram" token = "$TELEGRAM_BOT_TOKEN" # set via env or paste value ``` ### Multi-project config ```toml # Project 1: Claude on Telegram [project.dev] name = "dev" work_dir = "/home/user/project-a" data_dir = "/home/user/.cc-connect/data/dev" [project.dev.agent] type = "claude-code" [project.dev.platform] type = "telegram" token = "$TELEGRAM_BOT_TOKEN" # Project 2: Gemini on Feishu [project.research] name = "research" work_dir = "/home/user/project-b" data_dir = "/home/user/.cc-connect/data/research" [project.research.agent] type = "gemini" [project.research.platform] type = "feishu" app_id = "$FEISHU_APP_ID" app_secret = "$FEISHU_APP_SECRET" verification_token = "$FEISHU_VERIFICATION_TOKEN" ``` ### All supported platform types | `type` value | Platform | Public IP needed? | |---|---|---| | `telegram` | Telegram | No (long polling) | | `feishu` | Feishu / Lark | No (WebSocket) | | `dingtalk` | DingTalk | No (Stream) | | `slack` | Slack | No (Socket Mode) | | `discord` | Discord | No (Gateway) | | `wecom` | WeChat Work | No (WS) / Yes (Webhook) | | `line` | LINE | Yes (Webhook) | | `qq` | QQ via NapCat/OneBot | No | | `qqbot` | QQ Bot Official | No | | `weixin` | Personal WeChat (beta) | No (ilink long polling) | ### All supported agent types | `type` value | Agent | |---|---| | `claude-code` | Claude Code (Anthropic) | | `codex` | Codex (OpenAI) | | `cursor` | Cursor Agent | | `gemini` | Gemini CLI (Google) | | `qoder` | Qoder CLI | | `opencode` | OpenCode / Crush | | `iflow` | iFlow CLI | --- ## Platform-specific configuration ### Telegram ```toml [project.mybot.platform] type = "telegram" token = "$TELEGRAM_BOT_TOKEN" # Get token from @BotFather on Telegram # No public IP required — uses long polling ``` ### Feishu / Lark ```toml [project.mybot.platform] type = "feishu" app_id = "$FEISHU_APP_ID" app_secret = "$FEISHU_APP_SECRET" verification_token = "$FEISHU_VERIFICATION_TOKEN" # Uses WebSocket — no public IP needed # Set up at https://open.feishu.cn/ ``` ### Slack ```toml [project.mybot.platform] type = "slack" bot_token = "$SLACK_BOT_TOKEN" app_token = "$SLACK_APP_TOKEN" # app_token must start with xapp- (Socket Mode) # Enable Socket Mode in your Slack app settings ``` ### Discord ```toml [project.mybot.platform] type = "discord" token = "$DISCORD_BOT_TOKEN" # Uses Discord Gateway — no public IP needed ``` ### DingTalk ```toml [project.mybot.platform] type = "dingtalk" client_id = "$DINGTALK_CLIENT_ID" client_secret = "$DINGTALK_CLIENT_SECRET" # Uses DingTalk Stream — no public IP needed ``` ### WeChat Work (WeCom) ```toml [project.mybot.platform] type = "wecom" corp_id = "$WECOM_CORP_ID" agent_id = "$WECOM_AGENT_ID" secret = "$WECOM_SECRET" connection_type = "websocket" # websocket (no public IP) or webhook ``` ### Personal WeChat (beta only) ```bash # Install beta build first npm install -g cc-connect@beta # Scan QR code to log in cc-connect weixin setup ``` ```toml [project.mybot.platform] type = "weixin" # Auth state is stored after QR scan — no public IP needed ``` --- ## Running cc-connect ```bash # Default config location: ~/.cc-connect/config.toml cc-connect # Custom config path cc-connect --config /path/to/config.toml # Run specific project only cc-connect --project my-project ``` --- ## Chat Commands (sent in the messaging platform) | Command | Description | |---|---| | `/help` | Show all available commands | | `/model <name>` | Switch AI model (e.g. `/model claude-opus-4-5`) | | `/mode <mode>` | Change permission mode (e.g. `/mode auto`) | | `/reasoning <level>` | Tune reasoning intensity | | `/dir <path>` | Switch working directory for next session | | `/dir <number>` | Jump to a directory from history | | `/dir -` | Toggle to previous directory | | `/dir reset` | Restore configured `work_dir` | | `/cd <path>` | Alias for `/dir` | | `/memory` | Read or write the agent's memory/instruction file | | `/shell <cmd>` | Run a shell command (admin only) | | `/session` | Manage sessions (list, continue, new) | | `/continue` | Continue from last session (forks to avoid inheriting broken state) | | `/cron <spec> <task>` | Schedule a recurring task | | `/stop` | Stop the currently running agent | ### Slash command examples (in chat) ``` # Ask the agent to review a PR Review the changes in branch feature/auth and summarize the risks. # Switch to a different model /model gemini-2.0-flash # Change working directory /dir /home/user/other-project # Schedule a daily summary /cron 0 6 * * * Summarize GitHub trending Go repos and post here # Read agent memory /memory # Update agent memory /memory Always prefer table-driven tests in Go. Use context.Context for cancellation. ``` --- ## Multi-Agent Relay (group chat orchestration) Bind multiple bots in one group chat so they communicate with each other: ```toml # Bot 1: Claude [project.claude-bot] name = "claude-bot" work_dir = "/home/user/project" data_dir = "/home/user/.cc-connect/data/claude" [project.claude-bot.agent] type = "claude-code" [project.claude-bot.platform] type = "telegram" token = "$TELEGRAM_CLAUDE_BOT_TOKEN" # Bot 2: Gemini (same group) [project.gemini-bot] name = "gemini-bot" work_dir = "/home/user/project" data_dir = "/home/user/.cc-connect/data/gemini" [project.gemini-bot.agent] type = "gemini" [project.gemini-bot.platform] type = "telegram" token = "$TELEGRAM_GEMINI_BOT_TOKEN" ``` 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: ```toml [speech] provider = "openai" # openai | azure | google api_key = "$OPENAI_API_KEY" [speech.stt] mod
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.