-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
Telegram inbound stickers are not hydrated as agent-readable media #83748
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.no-staleExclude from stale automationExclude from stale automation
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.no-staleExclude from stale automationExclude from stale automation
Type
Fields
Priority
None yet
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_...webpattachments that could be inspected by the agent.Current behavior
In a Telegram direct chat, user sent a sticker. The agent context showed only:
When the agent attempted image analysis, the available temporary path was not usable from the sandbox/image tool:
Searching
/workspacedid 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:
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
2026.5.18 (50a2481)/workspaceopenai-codex/gpt-5.5Notes
Related but not necessarily duplicate: inbound media sharing / attachment metadata issues. This one is specifically Telegram sticker hydration into an agent-readable media path.