Execution engine stalls after login — loggedInUser null, /api/chats returns empty, no messages delivered

[yanghai45]

Environment

• agent-wechat versions tested: 0.11.9, 0.11.12, 0.11.15
• OpenClaw: 2026.4.1
• Host: Linux 5.15.0-174-generic (x64), Node 22.22.2
• Docker container: ghcr.io/thisnick/agent-wechat

Problem

After a successful QR code login, the execution engine reaches mainWindow=chat but stalls around step 22-23. The bridge never scrapes the chat list or
identifies the logged-in user.

Symptoms

1. /api/status/auth returns {"loggedInUser": null, "status": "logged_in"} — loggedInUser is always null
2. /api/chats returns [] indefinitely
3. /api/status returns {"loginState": {"status": "logged_out"}} even when /api/status/auth says logged_in (possible regression of The connection status for WeChat is constantly displaying incorrectly. #74)
4. Execution engine logs show stepping through mainWindow=chat then stops advancing — no errors
5. Gateway cannot deliver agent replies back to WeChat because chats are empty

Container logs pattern

[exec] step=21 mainWindow=chat, popup=none, contactCard=none, settings=none
[exec] step=22 mainWindow=chat, popup=none, contactCard=none, settings=none
[exec] step=23 mainWindow=chat, popup=none, contactCard=none, settings=none
[auth_status] view=Chat, status=logged_in
[auth_status] view=Chat, status=logged_in
... (no more exec steps, only periodic auth_status checks)

What was tried

• Fresh data volume (agent-wechat-data) — same result
• Versions 0.11.9, 0.11.12, 0.11.15 — same result on all
• Multiple logout/login cycles, both auto-login and QR code
• Gateway restart

Note

An earlier session (from a long-running container that had been up ~52 minutes) DID work — it could list chats, fetch messages, and the gateway successfully
dispatched and received replies. Every fresh login since then has hit this stall. The working session showed normal logs like:

wxid_xxx: fetched 20 msgs, firstPoll=true
Processing msg 53: type=1, sender=wxid_xxx, content=...
Dispatching segment: 1 msg(s), last=53

 {"loggedInUser":null,"status":"logged_in"}---CHATS---

[yanghai45]

fix-login-stall-153.patch

[denvey]

这个patch 没合并到主分支吗

[kyan-du]

Maintainer P0 Work Plan

A/B/C can proceed in parallel. D depends on A, B, and C being merged or otherwise available for validation.

• Package A — Owner: 春庭 (Kyan/assistant). Persistent idempotency + status API. Implementation package; expected output is one PR.
• Package B — Owner: Audrey. Redacted observability + Frida fallback diagnostics/tightening. Implementation package; expected output is one PR.
• Package C — Owner: Violet. Humanized sending/fair scheduling/template safeguards. Implementation package; expected output is one PR.
• Package D — Owner: Vangie. Isolated real regression and final acceptance after A/B/C. Validation/sign-off package; no code PR required unless fixes arise during validation.