Cc Bridge

Name: Cc Bridge
Rating: 3.5 (1 reviews)
Author: AliceLJY

By AliceLJY 👁 104 views ▲ 0 votes

OpenClaw plugin: Bridge Discord commands to local Claude Code — zero agent tokens, zero noise

GitHub

Configuration Example

{
  "plugins": {
    "entries": {
      "cc-bridge": {
        "enabled": true,
        "apiToken": "your-task-api-token",
        "callbackChannel": "your-discord-channel-id"
      }
    }
  }
}

README

# CC Bridge — OpenClaw Plugin

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
[![TypeScript](https://img.shields.io/badge/TypeScript-5.x-blue)](https://www.typescriptlang.org/)
[![OpenClaw](https://img.shields.io/badge/OpenClaw-Plugin-purple)](https://github.com/openclaw/openclaw)

> Bridge Discord slash commands to local Claude Code — zero agent tokens, zero noise.

> **CC Bridge** 把 Discord 命令直连本地 Claude Code，不消耗 agent token，不经过 AI 润色。你在 Discord 里发 `/cc 帮我查个 bug`，任务直接到你本机的 Claude Code，结果由 worker 回调到 Discord 频道。

## The Problem

Running Claude Code locally is powerful, but controlling it from your phone or another device means SSH tunnels, token juggling, or leaving a terminal open. OpenClaw bots can invoke tools, but every round-trip costs agent tokens — and the bot "helpfully" rephrases your CC output.

> 本地跑 Claude Code 很强，但想从手机远程操控就得折腾 SSH 隧道或者开着终端。OpenClaw bot 虽然能调工具，但每次都消耗 agent token，而且 bot 还"贴心地"把 CC 输出重新润色一遍。

## The Solution

CC Bridge registers Discord commands (`/cc`, `/cc-new`, `/cc-recent`, etc.) via OpenClaw's `registerCommand` API. Commands are handled **directly by the plugin** — no agent dispatch, no token cost, no AI rewriting. CC results are pushed back to Discord via [openclaw-worker](https://github.com/AliceLJY/openclaw-worker)'s callback mechanism.

> CC Bridge 通过 OpenClaw 的 `registerCommand` API 注册 Discord 命令。命令由插件直接处理——不经过 agent、不消耗 token、不被 AI 改写。CC 结果通过 [openclaw-worker](https://github.com/AliceLJY/openclaw-worker) 的回调机制推回 Discord。

## Architecture

```
Discord             OpenClaw Bot              CC Bridge Plugin        openclaw-worker         Claude Code
  |                     |                          |                       |                     |
  | /cc fix the bug     |                          |                       |                     |
  |-------------------->| registerCommand match     |                       |                     |
  |                     |------------------------->| POST /claude           |                     |
  |                     |                          |---------------------->| spawn session        |
  |                     |                          |                       |-------------------->|
  |                     |                          |                       |     ...working...    |
  |                     |                          |                       |<--------------------|
  |                     |    callback to Discord   |                       |                     |
  |<--------------------------------------------------------------------- |                     |
  |  (result in #cc)    |                          |                       |                     |
```

> - `/cc` 命令由 `registerCommand` 拦截，**不进入 agent 处理流程**（`shouldContinue: false`）
> - 任务通过 HTTP 提交给 openclaw-worker 的 Task API
> - CC 完成后，worker 直接用 Discord Bot API 推结果到指定频道
> - 全程零 agent token 消耗

## Commands

| Command | Description |
|---------|-------------|
| `/cc <prompt>` | Submit a task to Claude Code (auto-continues last session) |
| `/cc-new` | Reset session (next `/cc` starts fresh) |
| `/cc-new <prompt>` | Reset and immediately submit |
| `/cc-recent` | List recent CC sessions |
| `/cc-now` | Show current session ID |
| `/cc-resume <id> <prompt>` | Switch to a specific session and continue |

> 连续发 `/cc` 自动在同一会话里继续对话，不需要手动带 session ID。想换话题就用 `/cc-new`。

### Agent Tool: `cc_call`

CC Bridge also registers a `cc_call` tool for other channel agents. When an agent needs Claude Code assistance, it calls `cc_call` — the result is delivered directly to Discord via callback, not through the agent.

> `cc_call` 工具供其他频道的 agent 使用。agent 调用后结果由 worker 回调直推 Discord，不经过 agent 润色。

## Prerequisites

- [OpenClaw](https://github.com/openclaw/openclaw) bot running (Docker recommended)
- [openclaw-worker](https://github.com/AliceLJY/openclaw-worker) running locally with Task API enabled
- Claude Code installed locally (with Max subscription or API key)

> **作者环境**：MacBook Air M4 (16GB) · Docker 运行 OpenClaw bot · 本地 [openclaw-worker](https://github.com/AliceLJY/openclaw-worker) 提供 Task API · Claude Code (Max subscription) · Bun 运行时

## Installation

1. **Clone into your OpenClaw extensions directory:**

```bash
cd ~/.openclaw-<your-bot>/extensions/
git clone https://github.com/AliceLJY/openclaw-cc-bridge.git cc-bridge
```

2. **Configure in `openclaw.json`:**

Add the plugin config under `plugins.entries`:

```json
{
  "plugins": {
    "entries": {
      "cc-bridge": {
        "enabled": true,
        "apiToken": "your-task-api-token",
        "callbackChannel": "your-discord-channel-id"
      }
    }
  }
}
```

| Config Key | Required | Description |
|-----------|----------|-------------|
| `apiToken` | Yes | Auth token from your openclaw-worker config |
| `callbackChannel` | Yes | Discord channel ID where CC results are delivered |
| `apiUrl` | No | Task API URL (default: `http://host.docker.internal:3456`) |

3. **Restart your OpenClaw bot.** The plugin auto-registers on startup.

> `apiUrl` 默认指向 `host.docker.internal:3456`（Docker 容器访问宿主机）。如果 worker 不在本机，改成对应地址。

## How It Works

### Why `registerCommand` Instead of Agent Tools?

OpenClaw's `registerCommand` API registers text commands that are handled **before** the agent processes the message. When a command matches, the framework returns `shouldContinue: false` — the agent never sees the message. This means:

- **Zero token cost** — no LLM inference for command handling
- **Zero noise** — no AI rephrasing of CC output
- **Instant response** — no agent thinking time

> `registerCommand` 注册的命令在 agent 之前处理。匹配到命令后框架返回 `shouldContinue: false`，agent 根本看不到这条消息。

### Framework Gotcha: Space-Splitting

OpenClaw's `matchPluginCommand` splits command name from arguments **by space**. This means `/cc-recent` works (it's a registered command name), but `/cc最近` (no space) would fail to match `/cc` and fall through to the agent.

**Solution**: All subcommands use independent ASCII names (`cc-recent`, `cc-now`, `cc-new`, `cc-resume`) following the pattern established by [HappyClaw](https://github.com/rwmjhb/happyclaw).

> 框架用空格分割命令名和参数。`/cc最近`（连写、无空格）匹配不到 `/cc`，会穿透给 agent。解决方案：子命令用独立的 ASCII 命名，学自 HappyClaw 的设计模式。

## What's Different from HappyClaw?

[HappyClaw](https://github.com/rwmjhb/happyclaw) is a **PTY bridge** — it multiplexes local terminal sessions (Claude Code, Codex, Gemini CLI) and streams I/O to OpenClaw. CC Bridge takes a completely different approach:

| | HappyClaw | CC Bridge |
|--|-----------|-----------|
| **Mechanism** | PTY terminal multiplexing | HTTP Task API |
| **Scope** | Any CLI tool (Claude Code, Codex, Gemini) | Claude Code only (via openclaw-worker) |
| **Session model** | Persistent PTY processes | Stateless API calls with session ID tracking |
| **Unique feature** | Real-time terminal streaming | Auto-session continuation (just keep sending `/cc`) |
| **Design** | General-purpose bridge | Purpose-built for Claude Code + Discord workflow |

CC Bridge was born from a real daily workflow: controlling Claude Code from Discord on a phone while away from the desk. The **auto-session continuation** (no manual session ID juggling) and **dual-mode design** (slash commands for humans, `cc_call` tool for agents) came directly from dogfooding the tool.

> CC Bridge 诞生于真实的日常场景：离开电脑时用手机 Discord 远程操控本地 Claude Code。**自动会话续接**（不用手动带 session ID，连着发 `/cc` 就行）和**双模式设计**（命令给人用、cc_call 工具给 agent 用）都是在实际使用中磨出来的。HappyClaw 教会了我 `registerCommand` 的正确姿势，而 CC Bridge 是在这个基础上针对 Claude Code + Discord 场景的独立实现。

## Ecosystem

This plugin is part of a toolchain for controlling Claude Code from Discord:

| Project | Role |
|---------|------|
| [openclaw-worker](https://github.com/AliceLJY/openclaw-worker) | Local worker that bridges OpenClaw to Claude Code via Task API |
| [openclaw-cc-pipeline](https://github.com/AliceLJY/openclaw-cc-pipeline) | Multi-turn CC orchestration with human-in-the-loop review |
| [content-alchemy](https://github.com/AliceLJY/content-alchemy) | 7-stage content pipeline — a primary use case driven through CC |
| [openclaw-content-alchemy](https://github.com/AliceLJY/openclaw-content-alchemy) | Bot config kit for content publishing via OpenClaw |

## Acknowledgments

- **[HappyClaw](https://github.com/rwmjhb/happyclaw)** by [@rwmjhb](https://github.com/rwmjhb) — the PTY bridge plugin that pioneered the `registerCommand` pattern for OpenClaw. CC Bridge's architecture (ASCII subcommands, zero-token command handling, direct callback delivery) was directly inspired by studying HappyClaw's source code. Thank you for sharing!
- Built for the [OpenClaw](https://github.com/openclaw/openclaw) ecosystem
- Uses [openclaw-worker](https://github.com/AliceLJY/openclaw-worker) Task API for local Claude Code integration

> 特别感谢 [@rwmjhb](https://github.com/rwmjhb) 的 [HappyClaw](https://github.com/rwmjhb/happyclaw) 项目。CC Bridge 的架构设计（ASCII 子命令、零 token 命令处理、回调直推）直接学自 HappyClaw 的源码。开源社区的知识共享让每个人都能站在前人的肩膀上。

## Author

Built by **小试AI** ([@AliceLJY](https://github.com/AliceLJY)) · WeChat: **我的AI小木屋**

> 医学出身，文化口工作，AI 野路子。公众号六大板块：AI实操手账 · AI踩坑实录 · AI照见众生 · AI冷眼旁观 · AI胡思乱想 · AI视觉笔记

Six content pillars: **Hands-on AI** · **AI Pitfall Diaries** · **AI & Humanity** · **AI Cold Eye** · **AI Musings** · **AI Visual Notes**

Open-source byproducts: [content-alchemy](https://github.com/AliceLJY/content-alchemy) · [openclaw-worker](https://github.com/AliceLJY/openclaw-worker) · [openclaw-cc-pipeline](https://github.com/AliceLJY/openclaw-cc-pipeline) · [openclaw-content-alchemy](https://github.com/AliceLJY/openclaw-content-alchemy) · [digital-clone-skill](https://github.com/AliceLJY/digital-clone-skill)

<img src="./assets/wechat_qr.jpg" width="200" alt="WeChat QR Code">

---
v0.2.0 by Claude Code (Opus 4.6)

channels