openclaw - 💡(How to fix) Fix [Bug]: QQ Bot group chat replies silently lost — delivery routes to webchat instead of QQ

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

When a message is received in a QQ group chat, the agent processes it correctly but the reply is never sent back to the QQ group. The delivery pipeline silently routes the reply to the webchat session instead of calling the QQ Bot API.

This makes the QQ Bot channel receive-only for group conversations.

Root Cause

When a message is received in a QQ group chat, the agent processes it correctly but the reply is never sent back to the QQ group. The delivery pipeline silently routes the reply to the webchat session instead of calling the QQ Bot API.

This makes the QQ Bot channel receive-only for group conversations.

Code Example

[default] Processing message from DB814C937203D74C935913A1D79E3F72: 你好 {"type":"group","groupOpenid":"CAAC3E9D0D1C21018767EF4E6ED45CCA"}

---

{
  "key": "agent:main:qqbot:group:caac3e9d0d1c21018767ef4e6ed45cca",
  "origin": {
    "provider": "webchat",  // ← should be "qqbot"?
    "accountId": "default"
  },
  "deliveryContext": {
    "channel": "qqbot",
    "to": "qqbot:group:CAAC3E9D0D1C21018767EF4E6ED45CCA"
  }
}
RAW_BUFFERClick to expand / collapse

Bug: QQ Bot group chat replies silently lost — delivery pipeline routes to webchat instead of QQ

Environment

  • OpenClaw 2026.5.22 (macOS arm64)
  • QQ Bot channel plugin (appId: 1903751522)
  • Session: agent:main:qqbot:group:{groupOpenid}

Description

When a message is received in a QQ group chat, the agent processes it correctly but the reply is never sent back to the QQ group. The delivery pipeline silently routes the reply to the webchat session instead of calling the QQ Bot API.

This makes the QQ Bot channel receive-only for group conversations.

Steps to reproduce

  1. Configure QQ Bot channel with groupPolicy: "open"
  2. Add bot to a QQ group
  3. Send a message in the group (e.g. @bot 你好)
  4. Bot receives and processes the message (confirmed in gateway logs)
  5. Expected: Reply appears in the QQ group
  6. Actual: Reply is never delivered to QQ — no QQ Bot API POST calls in logs

Evidence from gateway logs

Inbound works:

[default] Processing message from DB814C937203D74C935913A1D79E3F72: 你好 {"type":"group","groupOpenid":"CAAC3E9D0D1C21018767EF4E6ED45CCA"}

Outbound — no API calls logged at all.

sessions_send misroutes: Sending to the QQ group session via sessions_send returns accepted with delivery.mode: "announce", but the message is delivered to the webchat session instead of the QQ group.

Session origin mismatch:

{
  "key": "agent:main:qqbot:group:caac3e9d0d1c21018767ef4e6ed45cca",
  "origin": {
    "provider": "webchat",  // ← should be "qqbot"?
    "accountId": "default"
  },
  "deliveryContext": {
    "channel": "qqbot",
    "to": "qqbot:group:CAAC3E9D0D1C21018767EF4E6ED45CCA"
  }
}

The origin.provider is "webchat" even though this is a QQ Bot group session. This likely causes the delivery router to fall back to webchat.

Related issues

  • #18864 — message tool send fails with "to required" when qqbot target is plain openid
  • #43779 — openclaw message send --channel qqbot --target fails with ToolInputError: to required
  • #77309 — 使用qqbot时Web端短回复不写session

Impact

QQ Bot group chat is completely non-functional for replies. Users can send messages to the bot but never receive responses.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING