rwcii

Codex Peer Bridge — Communication skill for Claude Code

Communication community

Local Unix-socket messaging bridge between Codex sessions and Claude Code peers.

How to install Codex Peer Bridge

This entry records only its repository, not the path inside it, so there is no exact command to give. Open rwcii/codex-peer-bridge and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Codex Peer Bridge does

Local Unix-socket messaging bridge between Codex sessions and Claude Code peers.

Alternatives in Communication

Lark Coding Agent Bridge — Bot that bridges Feishu/Lark messenger with a local Claude Code or Codex CLI 2.4k ★
Claude To IM — Host-agnostic bridge connecting Claude Code SDK to IM platforms (Telegram, Discord, Feishu) 432 ★
Pokegents — Pokegents is a local, Pokémon-inspired dashboard that turns Claude Code and Codex sessions into a local team d 95 ★

README

Codex Peer Bridge

A local bridge that lets an agent session exchange messages with Claude Code peers on the same machine. Claude discovers the bridge by name; a watcher notifies the selected participant session when messages arrive.

Python standard library only. No pip dependencies, cloud relay, or repository-specific integration.

Participants

The bridge speaks Claude's peer protocol on one side and hands notices to a selected participant session on the other. Two participant kinds are supported:

Participant	Session identity	Notice delivery
Codex	`CODEX_THREAD_ID`	`codex queue --thread ... --message ...`
DeepSeek (DSH)	`DSH_SESSION_ID`	`session/prompt` with `mode: "queue"` on the harness's local HTTP RPC

Both deliveries hand the session a content-free pointer notice that names the inbox and sequence range to read; neither carries peer text. A DeepSeek peer advertises the harness's configured default model in its peer name, such as `deepseek-v4-pro--a3`, and the model can be named explicitly with `session.py --model`.

How it works

flowchart LR
    Claude[Claude Code peer] <-->|Unix socket / NDJSON| Bridge[bridge.py]
    Bridge --> Inbox[(SQLite inbox)]
    Inbox --> Watcher[notify.py]
    Watcher -->|codex queue| Codex[Selected Codex thread]
    Watcher -->|session/prompt| DSH[Selected DeepSeek session]
    Codex -->|inbox / send commands| Bridge
    DSH -->|inbox / send commands| Bridge
    Watcher --> Registry[Claude local peer registry]

The bridge's server process originates outgoing connections as well as receiving incoming messages. This preserves the process identity Claude checks when routing replies. A separate private control socket lets a participant read the inbox and send messages through that process.

The watcher registers the live bridge as a named peer and queues a content-free notice to an explicitly selected session. The notification asks the participant to read the in