formulahendry/wechat-acp

Registry

Summary

A TypeScript-based bridge that connects WeChat chat messages to any ACP-compatible AI agent, including Claude, Codex, Copilot, Qwen, Gemini, OpenCode, OpenClaw, Hermes, Kiro, Kimi, pi, and more.

Key features

• Bridges WeChat messages to ACP-compatible AI agents
• Supports multiple agents: Claude, Codex, Copilot, Qwen, Gemini, and more
• Built with TypeScript for reliability and maintainability
• Implements the Agent Client Protocol (ACP) for standardized communication
• Open-source and community-driven

Use cases

• Integrate WeChat with Claude Skill for AI-powered chat responses
• Build a personal AI assistant accessible via WeChat
• Automate customer support by routing WeChat messages to AI agents
• Experiment with multiple AI models through a single WeChat interface
• Develop custom workflows combining WeChat and ACP-compatible agents

README excerpt

# WeChat ACP [](https://www.npmjs.com/package/wechat-acp) Bridge WeChat direct messages to any ACP-compatible AI agent. `wechat-acp` logs in with the WeChat iLink bot API, polls incoming 1:1 messages, forwards them to an ACP agent over stdio, and sends the agent reply back to WeChat. <img src="./resources/screenshot.jpg" alt="wechat-acp screenshot" width="400" /> ## Features - WeChat QR login with terminal QR rendering - One ACP agent session per WeChat user - Built-in ACP agent presets for common CLIs - Custom raw agent command support - Auto-allow permission requests from the agent - Direct message only; group chats are ignored - Background daemon mode ## Requirements - Node.js 20+ - A WeChat environment that can use the iLink bot API - An ACP-compatible agent available locally or through `npx` ## Quick Start Start with a built-in agent preset: ```bash npx -y wechat-acp@latest --agent copilot ``` Or use a raw custom command: ```bash npx -y wechat-acp@latest --agent "npx my-agent --acp" ``` On first run, the bridge will: 1. Start WeChat QR login 2. Render a QR code in the terminal 3. Save the login token under `~/.wechat-acp` 4. Begin polling direct messages ## Trying preview builds Every push to `main` is automatically published to npm under the `next` dist-tag, so you can try unreleased changes without waiting for a tagged release: ```bash npx -y wechat-acp@next --agent copilot ``` These versions are tagged `<base>-next.<UTC-timestamp>.<short-sha>` (e.g. `0.7.1-next.202605311530.abc1234`, where `0.7.1` is the next patch above whatever `@latest` is). They are built from `main` after CI passes, but have not been through a release review

Topics