Preserve Telegram sticker media paths
Fixed OpenClaw Telegram message context so cached static stickers and reply-chain media remain attachable to the agent while prompt text uses safe inbound media locators; later highlighted in the 2026.6.9 upstream digest's richer Telegram delivery notes.
openclaw/openclaw · #93130
Problem
Telegram inbound stickers could reach the agent only as provider file references or cached text, with no usable workspace media path for image/media tools. That made user-sent stickers opaque to the agent and also risked exposing raw local media-store paths in prompt-visible chat context.
Approach
Preserved saved sticker media paths in the runtime payload, kept reply-chain media attachable, skipped duplicate automatic understanding only for cached sticker descriptions, and canonicalized prompt-visible media paths to safe media://inbound/... locators.
Impact and scope
- Restores agent-readable media for Telegram static stickers, improving multimodal message handling in real chat workflows.
- Strengthens the prompt boundary by avoiding raw local filesystem paths and provider file references in transcript text.
- Improves reply-chain reliability by keeping runtime attachments usable while presenting stable, sanitized media locators to the model.
- Recognized in an OpenClaw upstream digest highlight for richer Telegram delivery in v2026.6.9-beta.1, with contributor thanks to @goutamadwant.
Validation
- Added cached static sticker media context regression coverage for MediaPath, MediaPaths, media type fields, and StickerMediaIncluded.
- Updated reply-chain and inbound metadata tests for canonical media://inbound locators, malformed path handling, and group visibility behavior.
- PR validation covered focused Vitest shards, TypeScript checks, formatting checks, diff checks, and clean local autoreview after maintainer follow-up.
- The June 19, 2026 upstream digest grouped #93130 under richer Telegram delivery and included @goutamadwant in the contributor thanks.