openclaw - 💡(How to fix) Fix [Bug]: Text reply after image attachment not delivered to Telegram in same turn (2026.4.21) [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#70222Fetched 2026-04-23 07:27:34
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Participants
Timeline (top)
closed ×1commented ×1labeled ×1

When an agent sends an image followed by text in the same turn, only the image is delivered to Telegram. The subsequent text response is visible in the Control UI but never sent via Telegram.

Root Cause

When an agent sends an image followed by text in the same turn, only the image is delivered to Telegram. The subsequent text response is visible in the Control UI but never sent via Telegram.

Code Example

# Gateway log - only one sendMessage after image, no subsequent text delivery
2026-04-22T22:09:43.127+08:00 [telegram] sendMessage ok chat=123456789 message=28817
2026-04-22T22:10:24.303+08:00 [telegram] sendMessage ok chat=123456789 message=28819

# Control UI backend shows Attachment unavailable followed by complete text response
# Text visible in backend but never sent to Telegram
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

When an agent sends an image followed by text in the same turn, only the image is delivered to Telegram. The subsequent text response is visible in the Control UI but never sent via Telegram.

Steps to reproduce

Ask the agent to generate an image and provide a description Agent sends image to Telegram ✅ Agent's follow-up text in the same turn is not delivered to Telegram ❌ Text is fully visible in Control UI backend

Expected behavior

Both the image and the follow-up text should be delivered to Telegram in the same turn.

Actual behavior

Only the image is delivered. The text response is visible in the Control UI but no sendMessage is triggered for it.

OpenClaw version

2026.4.21

Operating system

Rocky Linux

Install method

No response

Model

google/gemini-3-flash-preview

Provider / routing chain

google (direct, no proxy)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

# Gateway log - only one sendMessage after image, no subsequent text delivery
2026-04-22T22:09:43.127+08:00 [telegram] sendMessage ok chat=123456789 message=28817
2026-04-22T22:10:24.303+08:00 [telegram] sendMessage ok chat=123456789 message=28819

# Control UI backend shows Attachment unavailable followed by complete text response
# Text visible in backend but never sent to Telegram

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be fixed by modifying the code to handle multiple messages in the same turn, ensuring that both images and subsequent text are delivered to Telegram.

Guidance

  • Review the agent's message handling logic to identify why only the image is being sent to Telegram, while the subsequent text is visible in the Control UI but not delivered.
  • Check the sendMessage function to ensure it can handle multiple messages in the same turn, and consider modifying it to batch or queue messages for delivery.
  • Investigate the gateway log to understand why only two sendMessage events are recorded, despite the agent generating both an image and text response.
  • Verify that the issue is not related to the specific model (google/gemini-3-flash-preview) or provider (google) by testing with alternative configurations.

Example

No code snippet can be provided without more information about the agent's codebase, but a potential solution might involve modifying the message handling logic to use a loop or queue to send multiple messages in the same turn.

Notes

The issue may be related to the specific implementation of the agent's message handling logic, and further investigation is needed to determine the root cause. Additionally, the lack of information about the install method, provider/model setup details, and impact/severity makes it difficult to provide a more comprehensive solution.

Recommendation

Apply workaround: Modify the agent's message handling logic to handle multiple messages in the same turn, ensuring that both images and subsequent text are delivered to Telegram. This is recommended because it addresses the specific issue reported, although a more comprehensive solution may require additional information and testing.

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

Both the image and the follow-up text should be delivered to Telegram in the same turn.

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 [Bug]: Text reply after image attachment not delivered to Telegram in same turn (2026.4.21) [1 comments, 2 participants]