AliceLJY

Wechat AI Bridge — AI skill for Claude Code

AI community

Self-hosted WeChat bridge for Claude Code and Codex, with Claude tool approval and bidirectional file relay.

How to install Wechat AI Bridge

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

What Wechat AI Bridge does

Self-hosted WeChat bridge for Claude Code and Codex, with Claude tool approval and bidirectional file relay.

Alternatives in AI

Invisible Dots — Open-source, self-hosted alternative to OpenAI Dots, Meta Muse, Grok Bot, Manus Cue and Claude Cowork 31.8k ★
Hindsight — State-of-the-art long-term memory for AI agents by Vectorize 6.7k ★
Open Dots — Open-source, self-hosted AI agent workspace and alternative to OpenAI Dots, Meta Muse, Grok Bot, Instinct, Man 5.5k ★

README

wechat-ai-bridge

**Claude Code and Codex. In WeChat Private Chat.**

*Run local Claude Code or Codex agent sessions from WeChat, with Claude tool approval and file relay.*

A self-hosted bridge that uses WeChat's iLink bot endpoints. The WeChat transport itself needs no separate tunnel where iLink is available; each AI backend still needs its normal network access and account eligibility.

[![MIT License](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE) [![Version](https://img.shields.io/badge/version-1.2.0-green.svg)](https://github.com/AliceLJY/wechat-ai-bridge/releases) [![Bun](https://img.shields.io/badge/Runtime-Bun-f9f1e1?logo=bun)](https://bun.sh) [![WeChat](https://img.shields.io/badge/Interface-WeChat-07C160?logo=wechat)](https://weixin.qq.com/)

**English** | [简体中文](README_CN.md)

**How is this different from cc-weixin / wechat-acp?**

This project focuses on **session management** (`/new` `/resume` `/sessions`), **backend selection** (Claude + Codex), **Claude tool approval**, and **bidirectional file relay** — the same workflow family as [telegram-ai-bridge](https://github.com/AliceLJY/telegram-ai-bridge), now using WeChat transport.

**Do not use the `gemini` backend. This is an account-safety issue, not just a dead feature.**

This adapter reads `~/.gemini/oauth_creds.json` and reuses the Gemini CLI's own OAuth client to reach the internal Code Assist endpoint `cloudcode-pa.googleapis.com`. Google's FAQ names this exact pattern: *"Using third-party software, tools, or services to harvest or piggyback on Gemini CLI's OAuth authentication to access our backend services is a direct violation of our applicable terms and policies"*, and says it *"may be grounds for immediate suspension or termination of your account."* Paid subscribers have reportedly lost access over it. **This applies regardless of your plan tier — the prohibited thing is the mechanism, not the account type.**

Separa