Run Hermes Agent and OpenClaw on the same WeChat account
# Add to your Claude Code skills
git clone https://github.com/AaronWong1999/hermesclawDual-open Hermes Agent and OpenClaw on the same WeChat account. One command to install.
在同一个微信账号上同时双开 Hermes Agent 和 OpenClaw。一条命令安装。
Both Hermes Agent and OpenClaw now support WeChat natively — but you can't run both on the same account. Each gateway exclusively locks the iLink connection. If you start both, one gets 403 errors and drops messages.
HermesClaw solves this by becoming the sole iLink poller, then running two local proxy servers — one for each gateway. Each gateway believes it's talking to the real iLink API.
现在 Hermes 和 OpenClaw 都原生支持微信了——但你不能在同一个账号上双开。 每个 Gateway 会独占 iLink 连接。HermesClaw 解决这个问题：它作为唯一的 iLink 轮询者，运行两个本地代理，让两个 Gateway 各连各的。
Special thanks to the Hermes Agent team at Nous Research for recognizing and recommending HermesClaw in the Community section of their official GitHub README.
特别感谢 Nous Research 的 Hermes Agent 团队，在其 GitHub 官方 README 的 Community 区收录并推荐 HermesClaw。
Official reference: Hermes Agent README - Community
| | Without HermesClaw | With HermesClaw | |---|---|---| | Hermes on WeChat | ✅ Works (native gateway) | ✅ Works | | OpenClaw on WeChat | ✅ Works (clawbot) | ✅ Works | | Both on same account | ❌ Token conflict / 403 | ✅ mode | | Voice messages | ✅ Each handles natively | ✅ Transcription forwarded | | Images / video / files | ✅ Each handles natively | ✅ Raw iLink msg forwarded | | Switching agents | — | , , |
No comments yet. Be the first to share your thoughts!
/both/hermes/openclaw/both ┌────────── iLink API ──────────┐
│ ilinkai.weixin.qq.com │
└──────────┬────────────────────┘
│
(sole poller / token owner)
│
┌──────────▼────────────────────┐
│ HermesClaw v2 │
│ routes by /hermes /openclaw │
│ queues raw iLink messages │
├──────────┬────────────────────┤
│ │ │
Proxy A (:19999) Proxy B (:19998) │
for openclaw-weixin for hermes-gw │
│ │ │
▼ ▼ │
┌──────────┐ ┌──────────┐ │
│ openclaw │ │ hermes │ │
│ gateway │ │ gateway │ │
│ polls │ │ polls │ │
│ proxy A │ │ proxy B │ │
└────┬─────┘ └────┬─────┘ │
│ │ │
sendmessage sendmessage │
└─────┬──────┘ │
│ (proxy forwards to iLink)│
└─────────────────────────┘
HermesClaw is a thin Python proxy (~500 lines). It does not process media, call agent APIs, or touch agent memory. It just queues and forwards raw iLink protocol messages. Each gateway handles its own media decryption, markdown formatting, and AI interaction natively.
HermesClaw 只是一个轻量转发代理（~500 行），不处理媒体、不调 Agent API、不动记忆。每个 Gateway 原生处理自己的媒体解密和 AI 交互。
Before installing HermesClaw, you need at least one of:
openclaw-weixin) — installed and logged into WeChathermes gateway configuredBoth installed = full dual-open. One installed = single-agent mode with the option to add the other later.
安装 HermesClaw 前，需要至少安装以下其中一个：OpenClaw 的 clawbot，或者 Hermes 的微信 Gateway。
curl -fsSL https://raw.githubusercontent.com/AaronWong1999/hermesclaw/main/install.sh | bash
The installer will:
baseUrl → http://127.0.0.1:19999 (proxy A)WEIXIN_BASE_URL → http://127.0.0.1:19998 (proxy B)requests, python-dotenv)hermesclaw systemd serviceAfter install, restart your gateways and send /whoami in WeChat.
Drop this into any AI agent on the target machine:
Run: curl -fsSL https://raw.githubusercontent.com/AaronWong1999/hermesclaw/main/install.sh | bash
Then read README.md and install.sh from the installed HermesClaw directory.
Detect whether Hermes Agent, OpenClaw, their WeChat gateways, python3, pip3,
and systemd are present. At least one gateway must be configured. Extract
the iLink token from the first available gateway account file. Patch
openclaw-weixin baseUrl to http://127.0.0.1:19999 and Hermes WEIXIN_BASE_URL
to http://127.0.0.1:19998. Install dependencies and systemd service.
If Hermes Agent WeChat gateway is detected, the installer will offer to patch
weixin.py to disable newline-based message splitting (recommended). Accept
this patch so long replies are sent as single messages instead of being split
by paragraphs. The fix script is at fix_hermes_splitting.sh.
Restart gateways. Verify /whoami works in WeChat.
| Command | Action |
|---------|--------|
| /hermes | Route to Hermes only |
| /openclaw | Route to OpenClaw only |
| /both | Route to Hermes + OpenClaw (reply from both) |
| /whoami | Show current route and status |
| anything else | Forward to the active agent(s) |
Default route is Hermes. In /both mode, replies are prefixed with [Hermes Agent] / [OpenClaw] for attribution.
hermesclaw.py # ~500 lines. Dual-proxy router.
install.sh # Smart auto-detecting installer.
fix_hermes_splitting.sh # Patch Hermes weixin.py (optional, recommended).
tests/ # 59 pytest tests (core, proxy, recovery).
README.md
LICENSE
docs/ # Screenshots and media.
HermesClaw forwards raw iLink protocol messages to each gateway. This means:
HermesClaw does not do AES decryption, CDN downloads, or media re-encoding. That's each gateway's job.
Stop and disable the hermesclaw systemd service. Restore openclaw-weixin
account .bak files. Remove WEIXIN_BASE_URL override from ~/.hermes/.env
(or restore .bak). Optionally remove ~/hermesclaw directory.
sudo systemctl stop hermesclaw
sudo systemctl disable hermesclaw
sudo rm -f /etc/systemd/system/hermesclaw.service
sudo systemctl daemon-reload
# Restore openclaw-weixin configs:
find "$HOME" -maxdepth 5 -name "*.json.bak" -path "*/openclaw-weixin/accounts/*" \
-exec sh -c 'for f; do cp "$f" "${f%.bak}"; done' sh {} +
# Restore Hermes .env:
[ -f "$HOME/.hermes/.env.bak" ] && cp "$HOME/.hermes/.env.bak" "$HOME/.hermes/.env"
rm -rf "$HOME/hermesclaw"
weixin.py to disable newline-based message splitting during installation (recommended, default Yes). This ensures long replies are sent as single messages instead of being split by paragraphs. Existing users can run bash fix_hermes_splitting.sh manually.ThreadingHTTPServer instead of single-threaded HTTPServer.BrokenPipeError now caught and logged as DEBUG.MIT — by @AaronWong1999 · X @AaronYonW