[Bug]: QQ Bot C2C images downloaded successfully but attachments are missing from inbound message to Agent

Summary

When a user sends an image via QQ Bot C2C (private chat), the image file is downloaded to ~/.openclaw/media/qqbot/downloads/ successfully, but the Agent does not receive the attachment metadata in the inbound message. The message arrives as pure text with no attachments field, making the Agent unable to see or process the image.

This causes the Agent to miss images entirely and respond as if the image was never sent.

Bug type

Behavior bug (incorrect output/state without crash)

Steps to reproduce

1. Configure QQ Bot channel with C2C (private chat) messaging
2. Send an image from a QQ user to the bot (private chat, NOT group)
3. Check the Agent's received message in session transcript

Expected behavior

The Agent should receive a message with attachments array containing the image metadata:

{
  "type": "text",
  "text": "看 刚刚拍的",
  "attachments": [{
    "type": "image",
    "filename": "xxx.jpg",
    "url": "...",
    "localPath": "~/.openclaw/media/qqbot/downloads/xxx.jpg"
  }]
}

Actual behavior

The Agent receives ONLY the text part:

{
  "type": "text",
  "text": "看 刚刚拍的"
}

No attachments field is present. The image file IS downloaded to disk, but the attachment info is lost before reaching the Agent.

Evidence from session transcript

From the actual session transcript (agent:main:qqbot:direct:...), the user message at seq 455 shows:

{
  "role": "user",
  "content": [
    {
      "type": "text",
      "text": "看 刚刚拍的"
    }
  ],
  "timestamp": 1777721745498,
  "__openclaw": { "id": "4b05219c", "seq": 455 }
}

Note the absence of any attachments or image content. The Agent then replied as if the image was a sunset/warm sky, having no actual image data to analyze. Only after the user complained and the Agent manually used the read tool to load the local file did it see the actual image (which turned out to be a double rainbow).

Impact

• QQ Bot users cannot send images to the Agent
• Agent cannot analyze, describe, or respond to images
• This affects ALL image sending via QQ Bot C2C, not just specific file types
• The Agent appears to hallucinate image content because it has no visual data

Environment

Root Cause Analysis (Preliminary)

Based on code inspection of dist/extensions/qqbot/gateway-b6_B-JaX.js:

The gateway code does have attachments handling in the message entry building (lines 27-53, 137, 176, 197). However, the actual inbound event processing for QQ Bot C2C messages appears to not populate the attachments field from the QQ Bot event payload.

The image download works (files appear in ~/.openclaw/media/qqbot/downloads/), but the metadata linking the downloaded file to the inbound message is lost somewhere in the pipeline between:

1. QQ Bot event received
2. File downloaded
3. Message passed to Agent

This may be related to the C2C-specific event handler not extracting the attachment URLs from the QQ Bot message structure.

Related Issues

No existing issues found specifically about QQ Bot C2C image reception. The closest related issues are:

• #68016 — About sending images (outbound), not receiving
• #67062 — About media allowlist for outbound media SSRF policy
• #69546 — About QQ Bot routing bindings (unrelated)

Suggested Fix

1. Check the C2C message event handler in the QQ Bot adapter to ensure attachment URLs are extracted from the QQ Bot payload
2. Ensure the downloaded file path is linked to the message entry's attachments array
3. Verify the message builder includes attachments when constructing the Agent's inbound message