comm-bridge

name

comm-bridge

description

C4 communication bridge — central gateway for ALL external communication (Telegram, Lark, etc.). Use when replying to users via the "reply via" path, sending proactive messages to external channels, querying recent conversations or checkpoint status (prefer c4-db.js CLI; sqlite3 OK for unsupported queries), fetching conversation history for Memory Sync, or creating checkpoints after sync. Incoming messages are queued by channel bots and delivered to Claude via a PM2 dispatcher daemon. Session-start hooks automatically provide conversation context and can trigger Memory Sync when unsummarized conversations exceed the configured threshold.

Communication Bridge (C4)

Central message hub - ALL communication with Claude goes through C4.

Architecture

Web Console ──┐
Telegram    ───┼──► C4 Bridge ◄──► Claude
Lark        ───┘

Components

Script	Purpose	Reference
c4-receive.js	External → Claude (queue incoming messages)	c4-receive
c4-send.js	Claude → External (route outgoing messages)	c4-send
c4-control.js	System control plane (heartbeat, maintenance)	c4-control
c4-dispatcher.js	PM2 daemon: polls pending queue, delivers to tmux	—
c4-session-init.js	Hook (session start): context + Memory Sync trigger	hooks
c4-fetch.js