cc-connect

Bridge local AI coding agents (Claude Code, Cursor, Gemini CLI, Codex) to messaging platforms (Slack, Telegram, Discord). Use when: controlling AI agents from team chat, sending coding tasks via Slack/Telegram, building team-accessible AI workflows.

26 stars

Best use case

cc-connect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Bridge local AI coding agents (Claude Code, Cursor, Gemini CLI, Codex) to messaging platforms (Slack, Telegram, Discord). Use when: controlling AI agents from team chat, sending coding tasks via Slack/Telegram, building team-accessible AI workflows.

Teams using cc-connect should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/cc-connect/SKILL.md --create-dirs "https://raw.githubusercontent.com/TerminalSkills/skills/main/skills/cc-connect/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/cc-connect/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How cc-connect Compares

Feature / Agentcc-connectStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Bridge local AI coding agents (Claude Code, Cursor, Gemini CLI, Codex) to messaging platforms (Slack, Telegram, Discord). Use when: controlling AI agents from team chat, sending coding tasks via Slack/Telegram, building team-accessible AI workflows.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# CC-Connect

## Overview

CC-Connect bridges AI coding agents running on your local machine to the messaging platforms your team already uses. Code review, research, automation, data analysis — anything an AI agent can do, now accessible from your phone, tablet, or any device with a chat app.

**Architecture:** Your local AI agent <-> CC-Connect bridge <-> Messaging platform (Slack/Telegram/Discord/etc.)

Send a message in Slack, CC-Connect routes it to your local Claude Code instance, the agent does the work, and the response comes back to your chat.

## Instructions

### Installation

```bash
npm install -g cc-connect
```

### Configuration

Create a `cc-connect.yaml` in your project:

```yaml
agent:
  type: claude-code  # or: codex, gemini, cursor
  workdir: /path/to/your/project

platform:
  type: telegram  # or: slack, discord, feishu, dingtalk
  token: "your-bot-token"
```

### Platform Setup

**Telegram:** Create a bot via @BotFather, get the bot token, and add it to your config.

**Slack:** Create a Slack App at api.slack.com/apps, enable Socket Mode and Event Subscriptions, add Bot Token Scopes (`chat:write`, `app_mentions:read`, `messages.im`), and install to your workspace.

**Discord:** Create an application at discord.com/developers, create a bot, enable Message Content Intent, and invite the bot to your server.

### Starting the Bridge

```bash
cc-connect init    # Interactive wizard for platform credentials
cc-connect start   # Start routing messages
```

### Session Management

```yaml
session:
  timeout: 30m
  max_concurrent: 3
  continue: true
  auto_compress: true
```

### Multi-Agent Routing

Route different commands to different agents:

```yaml
agents:
  code-review:
    type: claude-code
    workdir: /path/to/project
    trigger: "!review"
  research:
    type: gemini
    trigger: "!research"
```

### Access Control

```yaml
access:
  allowed_users: ["U123", "U456"]
  allowed_channels: ["C789"]
  admin_users: ["U123"]
```

## Examples

### Example 1: Team Code Review via Slack

A team sets up CC-Connect to allow engineers to request code reviews from Slack:

```yaml
# cc-connect.yaml
agent:
  type: claude-code
  workdir: /home/dev/acme-api

platform:
  type: slack
  app_token: "xapp-1-A07QX4R..."
  bot_token: "xoxb-8234567890-..."
  channels: ["#code-review"]

session:
  timeout: 10m
  auto_compress: true

access:
  allowed_channels: ["#code-review"]
  allowed_users: ["U0381KDLS", "U0492JFMA"]
```

In Slack `#code-review`, an engineer types: `@agent Review the auth module for SQL injection risks`. Claude Code analyzes the code and responds in the thread with findings.

### Example 2: Scheduled Daily Reports via Telegram

A solo developer configures CC-Connect with cron jobs for automated daily standup reports:

```yaml
agent:
  type: claude-code
  workdir: /home/dev/saas-app

platform:
  type: telegram
  token: "7284619035:AAF-kLm9xPqR..."
  allowed_users: ["198274563"]

cron:
  - schedule: "0 9 * * 1-5"
    command: "Summarize yesterday's git commits and open PRs, highlight blockers"
    platform: telegram
    timeout: 5m
    fresh_session: true
```

Every weekday at 9am, the agent generates a summary of recent activity and sends it to the developer's Telegram chat.

## Guidelines

- Start with one messaging platform and get it working before expanding to others
- Always set `allowed_users` in production to restrict access
- Use threads in Slack/Discord to keep conversations organized
- Set `session.timeout` to prevent runaway agent sessions consuming resources
- Enable `auto_compress` for long conversations to prevent context overflow
- Use `fresh_session: true` for cron jobs to avoid inherited context from previous runs
- Verify your setup with `cc-connect status` if messages are not routing
- See the [GitHub Repository](https://github.com/chenhg5/cc-connect) for full documentation

Related Skills

stripe-connect

26
from TerminalSkills/skills

Build marketplace and platform payment flows with Stripe Connect. Use when: building two-sided marketplaces, splitting payments between buyers and sellers, onboarding sellers/providers to accept payments, handling platform fees and payouts, or managing connected accounts for a platform.

zustand

26
from TerminalSkills/skills

You are an expert in Zustand, the small, fast, and scalable state management library for React. You help developers manage global state without boilerplate using Zustand's hook-based stores, selectors for performance, middleware (persist, devtools, immer), computed values, and async actions — replacing Redux complexity with a simple, un-opinionated API in under 1KB.

zoho

26
from TerminalSkills/skills

Integrate and automate Zoho products. Use when a user asks to work with Zoho CRM, Zoho Books, Zoho Desk, Zoho Projects, Zoho Mail, or Zoho Creator, build custom integrations via Zoho APIs, automate workflows with Deluge scripting, sync data between Zoho apps and external systems, manage leads and deals, automate invoicing, build custom Zoho Creator apps, set up webhooks, or manage Zoho organization settings. Covers Zoho CRM, Books, Desk, Projects, Creator, and cross-product integrations.

zod

26
from TerminalSkills/skills

You are an expert in Zod, the TypeScript-first schema declaration and validation library. You help developers define schemas that validate data at runtime AND infer TypeScript types at compile time — eliminating the need to write types and validators separately. Used for API input validation, form validation, environment variables, config files, and any data boundary.

zipkin

26
from TerminalSkills/skills

Deploy and configure Zipkin for distributed tracing and request flow visualization. Use when a user needs to set up trace collection, instrument Java/Spring or other services with Zipkin, analyze service dependencies, or configure storage backends for trace data.

zig

26
from TerminalSkills/skills

Expert guidance for Zig, the systems programming language focused on performance, safety, and readability. Helps developers write high-performance code with compile-time evaluation, seamless C interop, no hidden control flow, and no garbage collector. Zig is used for game engines, operating systems, networking, and as a C/C++ replacement.

zed

26
from TerminalSkills/skills

Expert guidance for Zed, the high-performance code editor built in Rust with native collaboration, AI integration, and GPU-accelerated rendering. Helps developers configure Zed, create custom extensions, set up collaborative editing sessions, and integrate AI assistants for productive coding.

zeabur

26
from TerminalSkills/skills

Expert guidance for Zeabur, the cloud deployment platform that auto-detects frameworks, builds and deploys applications with zero configuration, and provides managed services like databases and message queues. Helps developers deploy full-stack applications with automatic scaling and one-click marketplace services.

zapier

26
from TerminalSkills/skills

Automate workflows between apps with Zapier. Use when a user asks to connect apps without code, automate repetitive tasks, sync data between services, or build no-code integrations between SaaS tools.

zabbix

26
from TerminalSkills/skills

Configure Zabbix for enterprise infrastructure monitoring with templates, triggers, discovery rules, and dashboards. Use when a user needs to set up Zabbix server, configure host monitoring, create custom templates, define trigger expressions, or automate host discovery and registration.

yup

26
from TerminalSkills/skills

Validate data with Yup schemas. Use when adding form validation, defining API request schemas, validating configuration, or building type-safe validation pipelines in JavaScript/TypeScript.

yt-dlp

26
from TerminalSkills/skills

Download video and audio from YouTube and other platforms with yt-dlp. Use when a user asks to download YouTube videos, extract audio from videos, download playlists, get subtitles, download specific formats or qualities, batch download, archive channels, extract metadata, embed thumbnails, download from social media platforms (Twitter, Instagram, TikTok), or build media ingestion pipelines. Covers format selection, audio extraction, playlists, subtitles, metadata, and automation.