openclaw - 💡(How to fix) Fix [Bug] openclaw-weixin: outbound push reports success but never delivers to personal WeChat accounts [2 comments, 2 participants]

Plugin: @tencent/openclaw-weixin Environment: macOS 25.4.0, OpenClaw latest, Node v22.16.0 Account Type: Personal WeChat (not 企业微信), bot_type=3 baseUrl: https://ilinkai.weixin.qq.com Account ID: e97a6e609973-im-bot User ID: [email protected]

Bug Description

Outbound push messages sent via openclaw-weixin channel always report "text sent OK" in Gateway logs and return HTTP success, but the messages are never received by the user's WeChat client.

This affects:

• Cron jobs (weather reminders, horoscope push, etc.)
• Any manual message sent via the message tool (outbound push mode)
• All independent proactive pushes

Important: Inbound works perfectly fine. The user can receive and send messages in conversation. Only outbound push is broken.

Steps to Reproduce

1. Set up openclaw-weixin plugin with a personal WeChat account (scan QR code login)
2. Create a cron job with channel set to openclaw-weixin
3. Wait for the cron job to trigger — or manually send a message via the message tool
4. Observe: Gateway logs show "text sent OK" but the user never receives the message

Gateway Log Evidence

gateway/channels/openclaw-weixin outbound: [email protected] contextToken=AARzJW...(len=136) textLen=194 mediaUrl=none
gateway/channels/openclaw-weixin outbound: text sent OK [email protected]

The contextToken (AARzJW...) is always the same, even after re-authentication.

Root Cause Investigation

Attempted fixes:

1. Re-authenticated via QR code (11:01 AM): New account e97a6e609973-im-bot was created. Gateway logs confirm:

   ✅ Login confirmed! [email protected]
   clearStaleAccountsForUserId: removing stale account=bdfa73875fac-im-bot
   clearContextTokensForAccount: cleared tokens for account=bdfa73875fac-im-bot

   But the new account's context-tokens.json file still contains the old contextToken (AARzJW...) — the token was not refreshed after new login.

2. Restarted Gateway: Cleared the context tokens file and restarted, but the old token is still used for sending.

3. Checked delivery-queue/failed/: Empty — the gateway believes all deliveries succeeded.

Files examined:

~/.qclaw/openclaw-weixin/accounts/e97a6e609973-im-bot.json
~/.qclaw/openclaw-weixin/accounts/e97a6e609973-im-bot.context-tokens.json

The account file was correctly updated with the new token after re-authentication, but the context token file was NOT updated with a new session token.

Technical Analysis

The openclaw-weixin plugin uses two types of tokens:

1. Account token ([email protected]:060000a3...) — stored in *.json, correctly refreshed after re-auth
2. Context token (AARzJW…, len=136) — stored in *.context-tokens.json, NOT refreshed after re-auth

The context token is used for the WebSocket session and outbound message sending. The bug appears to be:

The new QR code login successfully creates a new account and updates the account token, but does NOT fetch a new context token for the user session. The old context token (from before re-auth) is retained and reused, causing all outbound messages to fail silently.

Additionally: WeChat's API appears to accept these messages at the HTTP layer (returning success), but silently discards them because the context token is stale or invalid for outbound push.

Expected vs Actual Behavior

Environment Details

• OS: macOS 25.4.0 (arm64)
• Host: SoAK's Mac Studio
• Node: v22.16.0
• Gateway: launchd service (PID 91037)
• Plugin: @tencent/openclaw-weixin (built-in)
• baseUrl: https://ilinkai.weixin.qq.com
• bot_type: 3 (personal account)

Possible Fixes Needed

1. After QR code re-authentication, the plugin should fetch a new context token and update *.context-tokens.json
2. Or: detect stale context tokens and refresh them before sending outbound messages
3. Or: if personal WeChat accounts cannot support outbound push via this protocol, document this limitation clearly and show a warning/error instead of "sent OK"

Workaround

Users can fall back to asking the AI directly in conversation (inbound works fine). Cron job notifications need to be delivered via alternative channels (e.g., email) until this bug is fixed.