Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix agent --deliver can return mediaUrl payload without delivering Telegram media [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#77265•Fetched 2026-05-05 05:50:26
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
2
Author
joost-heijdenjoost-heijden
Participants
clawsweeper[bot]clawsweeper[bot]joost-heijdenjoost-heijden
Timeline (top)
commented ×1

openclaw agent --deliver can return a successful agent result containing mediaUrl/mediaUrls, but no Telegram media send appears to happen.

Manual openclaw message send --media with the same file and Telegram account succeeds.

Error Message

If openclaw agent --deliver returns a final payload with mediaUrl/mediaUrls and delivery channel/target/account are provided, it should deliver that media to Telegram or return an explicit delivery error. A silent success with an undelivered media payload is hard to diagnose.

Root Cause

openclaw agent --deliver can return a successful agent result containing mediaUrl/mediaUrls, but no Telegram media send appears to happen.

Manual openclaw message send --media with the same file and Telegram account succeeds.

Code Example

openclaw agent \
  --agent colorbestie \
  --deliver \
  --reply-channel telegram \
  --reply-account colorbestie \
  --reply-to <chat_id> \
  --message "Delivery smoke test: stuur deze bestaande afbeelding als media-payload, geen tekst-only. MEDIA:C:\Users\...\.openclaw\media\tool-image-generation\image.png" \
  --timeout 180 \
  --json

---

{
  "payloads": [
    {
      "text": "",
      "mediaUrl": "C:\\Users\\...\\.openclaw\\media\\tool-image-generation\\image.png",
      "mediaUrls": [
        "C:\\Users\\...\\.openclaw\\media\\tool-image-generation\\image.png"
      ]
    }
  ]
}

---

openclaw message send \
  --channel telegram \
  --account colorbestie \
  --target <chat_id> \
  --message "Here is the generated image" \
  --media "C:\Users\...\.openclaw\media\tool-image-generation\image.png" \
  --json

---

{
  "ok": true,
  "messageId": "9229",
  "chatId": "<chat_id>"
}
RAW_BUFFERClick to expand / collapse

Summary

openclaw agent --deliver can return a successful agent result containing mediaUrl/mediaUrls, but no Telegram media send appears to happen.

Manual openclaw message send --media with the same file and Telegram account succeeds.

Environment

  • OpenClaw: 2026.5.3-1
  • OS: Windows 11 / win32
  • Channel: Telegram direct chat
  • Account: Telegram account id colorbestie
  • Gateway: loopback, Scheduled Task service

Repro command

Using an existing local PNG generated by OpenClaw:

openclaw agent \
  --agent colorbestie \
  --deliver \
  --reply-channel telegram \
  --reply-account colorbestie \
  --reply-to <chat_id> \
  --message "Delivery smoke test: stuur deze bestaande afbeelding als media-payload, geen tekst-only. MEDIA:C:\Users\...\.openclaw\media\tool-image-generation\image.png" \
  --timeout 180 \
  --json

Observed result

The CLI returned status: ok with a payload like:

{
  "payloads": [
    {
      "text": "",
      "mediaUrl": "C:\\Users\\...\\.openclaw\\media\\tool-image-generation\\image.png",
      "mediaUrls": [
        "C:\\Users\\...\\.openclaw\\media\\tool-image-generation\\image.png"
      ]
    }
  ]
}

However, gateway logs did not show a corresponding Telegram sendPhoto/sendDocument/sendMessage entry for that delivery, and no media appeared in the chat from this agent --deliver invocation.

Control test

Sending the same file through the message command worked:

openclaw message send \
  --channel telegram \
  --account colorbestie \
  --target <chat_id> \
  --message "Here is the generated image" \
  --media "C:\Users\...\.openclaw\media\tool-image-generation\image.png" \
  --json

This returned:

{
  "ok": true,
  "messageId": "9229",
  "chatId": "<chat_id>"
}

Expected behavior

If openclaw agent --deliver returns a final payload with mediaUrl/mediaUrls and delivery channel/target/account are provided, it should deliver that media to Telegram or return an explicit delivery error. A silent success with an undelivered media payload is hard to diagnose.

extent analysis

TL;DR

The openclaw agent --deliver command may not be properly handling media delivery to Telegram, despite returning a successful result with mediaUrl/mediaUrls, and a workaround could be to use the openclaw message send command instead.

Guidance

  • Verify that the mediaUrl/mediaUrls paths are correct and the files exist, as the openclaw agent --deliver command seems to be returning a successful result with these paths.
  • Check the gateway logs for any errors or warnings related to media delivery, as the logs did not show a corresponding Telegram sendPhoto/sendDocument/sendMessage entry for the delivery.
  • Use the openclaw message send command as a workaround, as it successfully delivered the media to Telegram in the control test.
  • Investigate the differences in behavior between openclaw agent --deliver and openclaw message send to determine the root cause of the issue.

Example

No code snippet is provided as the issue is more related to the behavior of the openclaw commands rather than a specific code snippet.

Notes

The issue may be specific to the openclaw version 2026.5.3-1 or the Windows 11 environment, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Use the openclaw message send command instead of openclaw agent --deliver for media delivery to Telegram, as it has been shown to work in the control test.

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…

FAQ

Expected behavior

If openclaw agent --deliver returns a final payload with mediaUrl/mediaUrls and delivery channel/target/account are provided, it should deliver that media to Telegram or return an explicit delivery error. A silent success with an undelivered media payload is hard to diagnose.

#authentication issue#prompt issue#agent setup#task chaining#parallel task

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix agent --deliver can return mediaUrl payload without delivering Telegram media [1 comments, 2 participants]