Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Telegram inbound stickers are not hydrated as agent-readable media

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…

Telegram inbound stickers are no longer hydrated as accessible media attachments for the agent. The agent only receives a Telegram file/... sticker ref in conversation context, but no workspace/inbound media path that the image tool can read.

This appears to be a regression: earlier Telegram image/sticker-like media arrived as media/inbound/file_...webp attachments that could be inspected by the agent.

Root Cause

Agents often need to understand user-sent Telegram stickers/images in conversational context. Losing sticker hydration makes sticker messages opaque even though they were previously visible.

Code Example

<media:sticker> [sticker telegram:file/CAACAgUAAxkBAAKTL2n9OJFPxfggLPqSej4GP_xeDP2GAAIhHQACw1y5VRUqDk9No-bQOwQ]

---

Path escapes sandbox root (~/.openclaw/workspace; container root /workspace): /mnt/data/40297_image. Use a path under /workspace/ instead.

---

media/inbound/file_<n>---<uuid>.webp
RAW_BUFFERClick to expand / collapse

Summary

Telegram inbound stickers are no longer hydrated as accessible media attachments for the agent. The agent only receives a Telegram file/... sticker ref in conversation context, but no workspace/inbound media path that the image tool can read.

This appears to be a regression: earlier Telegram image/sticker-like media arrived as media/inbound/file_...webp attachments that could be inspected by the agent.

Current behavior

In a Telegram direct chat, user sent a sticker. The agent context showed only:

<media:sticker> [sticker telegram:file/CAACAgUAAxkBAAKTL2n9OJFPxfggLPqSej4GP_xeDP2GAAIhHQACw1y5VRUqDk9No-bQOwQ]

When the agent attempted image analysis, the available temporary path was not usable from the sandbox/image tool:

Path escapes sandbox root (~/.openclaw/workspace; container root /workspace): /mnt/data/40297_image. Use a path under /workspace/ instead.

Searching /workspace did not reveal a corresponding inbound sticker/image file. So the agent could not inspect the sticker.

Expected behavior

Inbound Telegram stickers should be downloaded/hydrated the same way as other inbound media, ideally exposing a stable relative media path such as:

media/inbound/file_<n>---<uuid>.webp

or another workspace-accessible path that image / file tools can read.

The visible context should include the attachment path/mime metadata, not only the provider telegram:file/... ref.

Why this matters

Agents often need to understand user-sent Telegram stickers/images in conversational context. Losing sticker hydration makes sticker messages opaque even though they were previously visible.

Environment

  • OpenClaw: 2026.5.18 (50a2481)
  • Channel: Telegram direct chat
  • Runtime: docker/all sandbox, workspace /workspace
  • Model session: openai-codex/gpt-5.5

Notes

Related but not necessarily duplicate: inbound media sharing / attachment metadata issues. This one is specifically Telegram sticker hydration into an agent-readable media path.

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

Inbound Telegram stickers should be downloaded/hydrated the same way as other inbound media, ideally exposing a stable relative media path such as:

media/inbound/file_<n>---<uuid>.webp

or another workspace-accessible path that image / file tools can read.

The visible context should include the attachment path/mime metadata, not only the provider telegram:file/... ref.

#model compatibility#GPU setup#container setup#orchestration issue#cache issue

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 Telegram inbound stickers are not hydrated as agent-readable media