openclaw - 💡(How to fix) Fix openclaw-weixin: runtime module scope isolation on 2026.5.4 [3 comments, 4 participants]

Description

After upgrading to OpenClaw 2026.5.4, the openclaw-weixin plugin (v2.4.1) fails with Weixin runtime initialization timeout. Debug logging shows setWeixinRuntime() succeeds but waitForWeixinRuntime() polls a different module instance where pluginRuntime stays NULL.

Root Cause

The pluginRuntime variable in runtime.js exists in two separate module scopes:

1. Scope A — register() → setWeixinRuntime(api.runtime) sets pluginRuntime ✅
2. Scope B — monitor.js → waitForWeixinRuntime() polls pluginRuntime which is NULL ❌

This is caused by OpenClaw 2026.5.4's plugin loader creating separate module instances for the same file path.

Additional: Content-Length header rejection

OpenClaw 2026.5.4 bundles undici 8.2.0 which rejects the plugin's Content-Length header:

InvalidArgumentError: invalid content-length header
  at processHeader (openclaw/node_modules/undici/lib/core/request.js:503)
  Cause code: UND_ERR_INVALID_ARG

Reproduction

openclaw --version              # 2026.5.4
openclaw plugins install @tencent-weixin/openclaw-weixin  # v2.4.1
openclaw channels login --channel openclaw-weixin
# Scan QR → timeout

Debug Logs

[runtime] setWeixinRuntime called, runtime set successfully
[runtime] waitForWeixinRuntime: pluginRuntime=NULL, start=1778056361184
[runtime] waitForWeixinRuntime: still waiting... 101ms, pluginRuntime=NULL
[runtime] waitForWeixinRuntime: still waiting... 2012ms, pluginRuntime=NULL
[runtime] waitForWeixinRuntime: TIMEOUT after 10058ms, pluginRuntime still NULL

Environment

• OpenClaw: 2026.5.4 (325df3e)
• Node.js: 22.22.1 (Gateway) / 24.15.0 (CLI)
• OS: WSL2 (Linux 6.6.87.2)
• Plugin: @tencent-weixin/[email protected]
• Bundled undici: 8.2.0