Track Tencent official Weixin plugin alignment and international WeChat login limits

[Sapientropic]

Summary

Keep Codeksei aligned with Tencent's official Weixin plugin and keep one public reminder about international / overseas WeChat login limits.

Current source-backed truth

• Codeksei now aligns its default CODEKSEI_WEIXIN_PROTOCOL_CLIENT_VERSION with @tencent-weixin/openclaw-weixin@2.1.8.
• Tencent's public docs currently say overseas WeChat support is region-gated, with Hong Kong supported and other regions still rolling out.
• Phone-side scan failures on international / overseas WeChat should not be assumed to be a local polling bug.

Follow-up checklist

• When Tencent publishes a newer @tencent-weixin/openclaw-weixin, review whether src/contracts/weixin-official.ts should be bumped.
• When Tencent expands or changes overseas support, update README / docs / login prompt wording.
• Re-run a real-device parity check against the official plugin before changing login defaults again.

Sources

• https://www.npmjs.com/package/@tencent-weixin/openclaw-weixin
• https://www.tencentcloud.com/techpedia/143910

[Sapientropic]

Status update as of April 18, 2026.

Quick read:

• There is still no source-backed evidence that Tencent has fully lifted the overseas / international WeChat rollout gate. Tencent's public docs still describe this as region-gated: Hong Kong is supported, while other overseas regions are still pending official rollout.
• Hermes-side WeChat / Weixin support is live on main, but media reliability fixes landed in multiple stages:
  • #7166 merged on April 10, 2026: native Weixin / WeChat support via the iLink Bot API
  • #8665 merged on April 12, 2026: fixes for streaming cursor behavior, media uploads, markdown links, and blank-message guards
  • #11478 merged on April 17, 2026: fixes send_image_file(image_path=...) signature mismatch that was still causing dropped image sends
• Tencent's official plugin is still at @tencent-weixin/openclaw-weixin@2.1.8 on npm (published April 10, 2026). The official plugin repo still has fresh open bugs around duplicate media sends (Tencent/openclaw-weixin#74) and long-poll timeout handling (Tencent/openclaw-weixin#75).

What this means for Codeksei:

• This issue should stay open as a tracking issue.
• We should not treat international / overseas scan failures as proof of a local polling bug.
• If we update Hosted Mode / Hermes guidance again, we should re-check against Hermes main or the next release after April 17, 2026, not just v0.10.0 (v2026.4.16), because the latest image-send fix landed after that release.
• For Codex Mode / first-party adapter docs, we should keep the public reminder that Hong Kong is supported and other overseas regions remain rollout-dependent.

Source-backed details:

• Tencent public doc (created April 7, 2026; updated April 9, 2026) still says overseas support is only available in some regions, with Hong Kong supported and other regions pending official rollout. The same doc also says the currently supported mobile versions are iOS 8.0.70+ and Android 8.0.69+, and desktop WeChat is not supported.
• Tencent's public FAQ also marks one "QR code cannot be generated / protocol failed too many times" path as "resolved", but the public page truncates the exact command snippet, so I am not treating that as a reusable public fix recipe yet.
• Hermes feature thread NousResearch/hermes-agent#2422 was closed on April 12, 2026, with maintainer confirmation that native WeChat / Weixin support is live on main and that follow-up media / upload / formatting fixes were merged in #8665.
• Hermes media follow-ups:
  • #8783 reported the adapter media-signature mismatch on April 13, 2026
  • #8781 proposed the fix
  • maintainers closed #8781 as duplicate after merging #11478 on April 17, 2026
• Tencent / OpenClaw-side recent state:
  • Tencent/openclaw-weixin#3 (inbound image CDN 500) was marked fixed on April 2, 2026
  • Tencent/openclaw-weixin#74 (duplicate image send for the same file) is still open
  • Tencent/openclaw-weixin#75 (UND_ERR_HEADERS_TIMEOUT treated as a hard failure in long-poll) is still open
  • Tencent/openclaw-weixin#71 / #72 suggest the published tarball still ships TypeScript sources and may contribute to slow / high-CPU startup in some environments
• Separate from the overseas rollout question, there are also source-backed reports that some "no QR code appears" failures were host-side or plugin-side regressions rather than region gating:
  • openclaw/openclaw#56552: plugin-side QR-start timeout / AbortError path
  • openclaw/openclaw#62120: host-side preflight regression before plugin login starts

Community workaround worth watching:

• AaronWong1999/hermesclaw is a community bridge that acts as a single iLink poller and proxies both Hermes and OpenClaw to the same WeChat account. It looks useful for the "same account dual-open / 403 token conflict" case, but it is a community bridge, not an official fix for rollout gating or plugin bugs.

References:

• Sapientropic/codeksei#8
• npm: @tencent-weixin/openclaw-weixin
• Tencent doc: https://www.tencentcloud.com/techpedia/143910
• Hermes: NousResearch/hermes-agent#2422, #7166, #8665, #8783, #8781, #11478
• Tencent plugin: Tencent/openclaw-weixin#3, #71, #74, #75
• OpenClaw host/plugin issues: openclaw/openclaw#56552, #62120
• Community bridge: AaronWong1999/hermesclaw