ClawBridge for WeChat — ChatGPT Work, project chat, and explicit read-only Codex from WeChat

[samzhou1972]

I built ClawBridge for WeChat, a small local-first bridge for a workflow I use on my Windows development PC.

My use case is fairly specific: WeChat is already the communication channel I keep open on my phone, and I wanted one lightweight entry point for three separate things:

• /work — observe local ChatGPT Work status and results;
• /chat — continue discussing the current local project with ChatGPT and lightweight project context;
• /codex — explicitly start Codex CLI analysis against a configured repository in a read-only sandbox.

The execution boundary is deliberate.

A normal /chat request does not silently turn into local code execution. Codex only runs when /codex is explicitly invoked, using:

codex exec --sandbox read-only

Detailed logs, source code, long outputs, browser state, and runtime state remain on the PC. WeChat is mainly the control, short-result, and notification channel.

The latest v0.1.1 release also adds:

python -m clawbridge doctor

It checks the local config, configured projects, WeChat binding, Chrome / ChatGPT profile, and Codex CLI availability without treating optional capabilities as hard failures.

Current status:

• MIT licensed
• Alpha / Early Stage
• complete first-time setup verified on Windows
• supervised real WeChat E2E verified
• 130 automated tests passing

Repository:

https://github.com/samzhou1972/clawbridge-wechat

Disclosure: I maintain ClawBridge and use it in my own local Windows development workflow.

I’d especially value feedback on the boundary between a lightweight messaging bridge and a full remote development interface.

[samzhou1972]

A quick visual of the current /chat workflow in WeChat:

The first screenshot shows a project-level question from WeChat. The second shows a more detailed response while keeping the conversation tied to the selected local project.