Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Telegram outbound images sent via read tool render locally but never reach recipient's mobile client [1 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#63137•Fetched 2026-04-09 07:58:00
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
niccoreyesniccoreyes
Participants
niccoreyesniccoreyes
Timeline (top)
mentioned ×1subscribed ×1

While testing a website screenshot workflow (capture screenshot → send to Telegram), I discovered that images sent by an OpenClaw agent via the tool appear in the agent's context but never arrive on the recipient's Telegram mobile client. The failure is silent — no errors in logs.

Error Message

  • ❌ Zero error logs — completely silent failure

Root Cause

While testing a website screenshot workflow (capture screenshot → send to Telegram), I discovered that images sent by an OpenClaw agent via the tool appear in the agent's context but never arrive on the recipient's Telegram mobile client. The failure is silent — no errors in logs.

Fix Action

Fix / Workaround

Impact and severity

  • Use case blocked: Automated website screenshot delivery to Telegram
  • Severity: Medium-High (breaks image-based agent workflows)
  • Frequency: 5/5 attempts (100% reproducible)
  • Consequence: Cannot build screenshot → Telegram delivery pipelines; requires Google Drive workaround

Additional information

  • Silent failure: No gateway logs, no failed delivery queue entries
  • Workaround: Upload to Google Drive and share link (works reliably)
  • Environment: Raspberry Pi 4, Telegram mobile client (iOS/Android), @niccoreyes
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

While testing a website screenshot workflow (capture screenshot → send to Telegram), I discovered that images sent by an OpenClaw agent via the tool appear in the agent's context but never arrive on the recipient's Telegram mobile client. The failure is silent — no errors in logs.

Steps to reproduce

  1. Goal: Test automated website screenshots delivered to Telegram
  2. Install skill:
  3. Capture screenshot: API captures →
  4. Agent sends image: Uses tool on PNG file targeting Telegram chat ID 637237233
  5. Observe: Image renders in agent context (agent can see it)
  6. Check: Recipient's Telegram mobile client — image never appears

Expected behavior

Captured screenshot should appear as a viewable photo in the recipient's Telegram mobile chat, enabling automated website screenshot delivery workflows.

Actual behavior

  • ✅ Image renders in agent context (verified via tool output)
  • ❌ Image never appears on recipient's Telegram mobile client
  • ❌ Zero error logs — completely silent failure
  • ❌ CLI with exits with SIGKILL
  • Tested: PNG files, renamed extension, multiple sends — all fail silently

OpenClaw version

2026.4.5 (3e72c03)

Operating system

Raspberry Pi OS (Debian-based, arm64)

Install method

npm global

Model

fireworks/accounts/fireworks/routers/kimi-k2p5-turbo

Provider / routing chain

openclaw -> fireworks

Logs, screenshots, and evidence

Impact and severity

  • Use case blocked: Automated website screenshot delivery to Telegram
  • Severity: Medium-High (breaks image-based agent workflows)
  • Frequency: 5/5 attempts (100% reproducible)
  • Consequence: Cannot build screenshot → Telegram delivery pipelines; requires Google Drive workaround

Additional information

  • Silent failure: No gateway logs, no failed delivery queue entries
  • Workaround: Upload to Google Drive and share link (works reliably)
  • Environment: Raspberry Pi 4, Telegram mobile client (iOS/Android), @niccoreyes

extent analysis

TL;DR

Verify the Telegram chat ID and API configuration to ensure correct image delivery from the OpenClaw agent.

Guidance

  • Check the Telegram chat ID (637237233) for correctness and ensure it matches the intended recipient's chat ID.
  • Review the OpenClaw agent's configuration and the tool's settings to confirm that the image is being sent to the correct Telegram chat ID.
  • Investigate potential issues with the OpenClaw agent's API or the Telegram API that might be causing the silent failure.
  • Consider testing the image delivery with a different chat ID or a different Telegram client to isolate the issue.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue lacks information about the specific API calls and configurations used by the OpenClaw agent and the tool. Additional logging or debugging might be necessary to identify the root cause of the issue.

Recommendation

Apply workaround: Upload images to Google Drive and share the link, as this approach has been reported to work reliably, until the root cause of the issue with the OpenClaw agent and Telegram delivery can be identified and resolved.

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

Captured screenshot should appear as a viewable photo in the recipient's Telegram mobile chat, enabling automated website screenshot delivery workflows.

#api#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

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

Back to top recommendations

TRENDING