You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
Environment
Problem
After a successful QR code login, the execution engine reaches
mainWindow=chatbut stalls around step 22-23. The bridge never scrapes the chat list oridentifies the logged-in user.
Symptoms
/api/status/authreturns{"loggedInUser": null, "status": "logged_in"}—loggedInUseris alwaysnull/api/chatsreturns[]indefinitely/api/statusreturns{"loginState": {"status": "logged_out"}}even when/api/status/authsayslogged_in(possible regression of The connection status for WeChat is constantly displaying incorrectly. #74)mainWindow=chatthen stops advancing — no errorsContainer 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
agent-wechat-data) — same resultNote
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---