openclaw - 💡(How to fix) Fix [Bug]: Yuanbao group chat: model output routed to wrong session (direct queue instead of group queue) — replies never sent to group [1 comments, 2 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Group chat @mention triggers model generation but the reply is queued in the direct session's outbound buffer (agent:main:yuanbao:direct:...) instead of the group session's buffer (agent:main:yuanbao:group:387668713), causing the group to receive no reply while direct chat receives it.

Steps to reproduce

Add OpenClaw Yuanbao bot to a Yuanbao group Send any message @mentioning the bot in the group Observe: bot receives the message (gateway log shows isGroup:true, isAtBot:true) Bot never replies in group — same bot replying normally in direct/private chat

Expected behavior

Group session outbound queue receives the model output and sends via [GROUP] send to the group.

Actual behavior

Gateway log shows agent:main:yuanbao:group:387668713 merge-text session flush: bufLen=0 (group queue empty) Gateway log shows agent:main:yuanbao:direct:... merge-text push: bufLen=N (direct queue receives the output) Transport sends via [C2C] send ok (private chat) instead of [GROUP] send ok Model output confirmed generated: dispatch-reply received reply data {"kind":"block","model_output":"Gat**** 🦐"}

OpenClaw version

v2026.4.27

Operating system

macOS (Darwin)

Install method

npm global install via Homebrew (brew install openclaw)

Model

minimax-portal/MiniMax-M2.7

Provider / routing chain

OpenClaw gateway → yuanbao plugin v2.12.0 → WebSocket → MiniMax OAuth portal (coding plan)

Additional provider/model setup details

{

"channels": {

"yuanbao": {

  "appKey": "NIrb9w0ZvpKuX4Dm9tXKuIn7q4zzq2L0",

  "enabled": true,

  "groupPolicy": "open"

}

},

"bindings": [

{ "agentId": "main", "match": { "channel": "yuanbao", "peer.kind": "group" } },

{ "agentId": "main", "match": { "channel": "yuanbao", "peer.kind": "direct" } }

]

}

Both group and direct use main agent. Direct chat works fine with identical config.

Logs, screenshots, and evidence

// Group message received correctly
[pipeline] [extract-content] received message {"isGroup":true,"from":"...","nickname":"KingSword","groupCode":"387668713","msgSeq":144,"isAtBot":true}
// Group session queue is EMPTY
[yuanbao][outbound-queue] [agent:main:yuanbao:group:387668713] merge-text session flush: bufLen=0
// Model output routed to WRONG queue (direct)
[yuanbao][outbound-queue] [agent:main:yuanbao:direct:5b6lRXcVt4D+.../] merge-text push: bufLen=37
// Sent as private message instead of group
[yuanbao][transport] [C2C] send ok {"toAccount":"...","msgId":"7b92623bd6bb47f28a5e866303e2e5f2"}
// Model DID generate output
[pipeline] [dispatch-reply] received reply data {"kind":"block","model_output":"Gat**** 🦐"}
// dispatch-reply completes for group (with empty queue)
[pipeline] [dispatch-reply] message processing complete {"isGroup":true,"groupCode":"387668713","fromAccount":"..."}

Impact and severity

Severity: High — group chat is completely non-functional for this Yuanbao bot. Direct chat works fine. No workaround found (model switch, groupPolicy change, session reset all tried without success). Consistent repro: 100% of group @mentions fail to reply in group.

Additional information

No response