Summary

• Keeps cached static Telegram sticker media attached to inbound context instead of dropping the saved media path when a sticker cache hit supplies text.
• Preserves hydrated reply-chain media as attachable runtime paths while rendering prompt-visible media locators as stable media://inbound/... references.
• Avoids exposing raw local media-store paths in chat-window prompt text and avoids leaking Telegram provider file refs when a safe hydrated path is available.
• Removes the stale sticker-media prune helper that made cached sticker media disappear before dispatch.

What problem does this PR solve?

Telegram static stickers could reach the agent as cached sticker text with no usable MediaPath, so image/media tools could not inspect the underlying sticker media.

Why does this matter now?

Issue #83748 is a P2 queued fix for Telegram message-loss behavior where inbound sticker media is not available to the agent.

What is the intended outcome?

Static Telegram sticker media remains available as inbound media for the current turn, and prompt-visible reply/conversation media uses safe media://inbound/... references instead of raw local paths or provider file ids.

What is intentionally out of scope?

Animated TGS/video WEBM sticker support, live Telegram transport changes, and broader Telegram photo behavior outside the sticker/reply-chain path.

What does success look like?

Cached static stickers still provide MediaPath/MediaPaths, reply-chain media remains attachable through the runtime payload, and prompt chat windows do not expose raw local media-store paths.

What should reviewers focus on?

Telegram media context boundaries: cached current-message stickers, direct vs group reply-chain prompt context, and canonicalization of media_path values in inbound-meta.

Linked context

Which issue does this close?

Closes #83748

Which issues, PRs, or discussions are related?

Related #84599

Was this requested by a maintainer or owner?

No direct maintainer assignment. This was selected from the #84599 contributor queue context and the #83748 ClawSweeper labels (queueable-fix, fix-shape-clear, source-repro).

Real behavior proof (required for external PRs)

• Behavior or issue addressed: Telegram cached static sticker media and hydrated reply-chain media now keep agent-readable media paths while prompt text gets canonical media://inbound/... locators.
• Real environment tested: Local OpenClaw source checkout on macOS with Node 22.22.3 from a local node toolchain path, redacted here as <local-node-bin>.
• Exact steps or command run after this patch:
  • PATH="<local-pnpm-shim>:<local-node-bin>:/usr/bin:/bin:/usr/sbin:/sbin:$PATH" corepack pnpm exec tsx --eval '<production buildTelegramMessageContext sticker payload script>'
  • PATH="<local-pnpm-shim>:<local-node-bin>:/usr/bin:/bin:/usr/sbin:/sbin:$PATH" corepack pnpm exec tsx --eval '<production buildInboundUserContextPrefix media_path rendering script>'
  • PATH="<local-node-bin>:/usr/bin:/bin:/usr/sbin:/sbin:$PATH" node scripts/run-vitest.mjs src/auto-reply/reply/inbound-meta.test.ts extensions/telegram/src/bot-message-context.sticker-media.test.ts extensions/telegram/src/bot.test.ts extensions/telegram/src/message-cache.test.ts extensions/telegram/src/bot.media.stickers-and-fragments.e2e.test.ts src/agents/tools/image-tool.test.ts src/auto-reply/media-note.test.ts
  • PATH="<local-node-bin>:/usr/bin:/bin:/usr/sbin:/sbin:$PATH" corepack pnpm tsgo:extensions
  • PATH="<local-node-bin>:/usr/bin:/bin:/usr/sbin:/sbin:$PATH" corepack pnpm tsgo:core
  • PATH="<local-node-bin>:/usr/bin:/bin:/usr/sbin:/sbin:$PATH" corepack pnpm exec oxfmt --check --threads=1 src/auto-reply/reply/inbound-meta.ts src/auto-reply/reply/inbound-meta.test.ts extensions/telegram/src/bot-handlers.runtime.ts extensions/telegram/src/bot-message-context.session.ts extensions/telegram/src/bot-message-context.ts extensions/telegram/src/bot-message-dispatch.ts extensions/telegram/src/bot-message-context.sticker-media.test.ts extensions/telegram/src/bot.test.ts
  • /usr/bin/git diff --check
  • PATH="<local-node-bin>:/usr/bin:/bin:/usr/sbin:/sbin:$PATH" .agents/skills/autoreview/scripts/autoreview --mode local
• Evidence after fix (screenshot, recording, terminal capture, console output, redacted runtime log, linked artifact, or copied live output):
  • Terminal capture from production buildTelegramMessageContext in the local OpenClaw checkout:

    REAL_OPENCLAW_STICKER_PROOF_BEGIN
    {
      "Body": "[Telegram Ada id:777 Wed 2025-01-08 16:00:00 PST] Ada: <media:image>",
      "MediaPath": "<redacted-media-store>/media/inbound/sticker.webp",
      "MediaType": "image/webp",
      "MediaPaths": [
        "<redacted-media-store>/media/inbound/sticker.webp"
      ],
      "MediaTypes": [
        "image/webp"
      ],
      "StickerMediaIncluded": true,
      "StickerFileUniqueId": "sticker_unique_789"
    }
    REAL_OPENCLAW_STICKER_PROOF_END
    

  • Terminal capture from production buildInboundUserContextPrefix in the local OpenClaw checkout:

    REAL_OPENCLAW_PROOF_BEGIN
    Current local chat window (untrusted, chronological, before current message):
    #9000 Ada: previous sticker [image/webp media://inbound/previous-sticker.webp]
    REAL_OPENCLAW_PROOF_END
    

  • Supplemental validation: [test] passed 5 Vitest shards in 144.81s; tsgo:extensions and tsgo:core exited 0; direct oxlint on the changed files exited 0; oxfmt --check and /usr/bin/git diff --check exited 0.
• Observed result after fix: Cached static sticker context keeps MediaPath, MediaType, MediaPaths, MediaTypes, and StickerMediaIncluded. Prompt-visible chat-window context renders media://inbound/... instead of the raw local media-store path or provider file ref. Runtime ReplyChain[].mediaPath stays local/attachable, and group chat-window context does not receive pre-visibility local media paths.
• What was not tested: Live Telegram bot traffic with real Telegram credentials, docker/all, Crabbox, animated TGS stickers, and video WEBM stickers.
• Proof limitations or environment constraints: This proof uses a local OpenClaw source checkout with production module calls, minimal runtime stubs, and redacted local paths rather than a live Telegram account. No private Telegram bot token was available or used.
• Before evidence (optional but encouraged): Before this patch, cached sticker descriptions triggered sticker-media pruning before dispatch, so the context could keep sticker text while losing the saved media path that agent media tools need.

Tests and validation

Which commands did you run?

• Production tsx --eval command for buildTelegramMessageContext sticker payload proof.
• Production tsx --eval command for buildInboundUserContextPrefix prompt rendering proof.
• Focused Vitest command listed above.
• corepack pnpm tsgo:extensions
• corepack pnpm tsgo:core
• corepack pnpm exec oxfmt --check --threads=1 ...
• /usr/bin/git diff --check
• .agents/skills/autoreview/scripts/autoreview --mode local
• corepack pnpm exec oxlint src/auto-reply/reply/inbound-meta.ts extensions/telegram/src/bot-handlers.runtime.ts extensions/telegram/src/bot-message-context.session.ts extensions/telegram/src/bot-message-context.sticker-media.test.ts

What regression coverage was added or updated?

• Added a cached static sticker media context regression covering MediaPath, MediaPaths, media type/url fields, and StickerMediaIncluded.
• Updated Telegram reply-chain tests to verify runtime media paths stay attachable while structured prompt context uses canonical media://inbound/... locators.
• Updated group chat context coverage so hydrated reply media does not bypass group visibility filtering.
• Added auto-reply formatter coverage for absolute media-store paths, malicious-looking canonical media ids, and already-encoded canonical ids that must not be double-encoded.

What failed before this fix, if known?

Cached sticker descriptions caused sticker media to be pruned from the dispatch context, leaving no agent-readable saved media path for static sticker inspection.

If no test was added, why not?

Not applicable. Focused regression tests were added and updated.

Risk checklist

Did user-visible behavior change? (Yes/No)

Yes.

Did config, environment, or migration behavior change? (Yes/No)

No.

Did security, auth, secrets, network, or tool execution behavior change? (Yes/No)

Yes. Prompt-visible media locator handling was tightened so local filesystem paths are not rendered and untrusted media_path values are canonicalized before transcript rendering. No auth, secrets, network, or tool execution behavior changed.

What is the highest-risk area?

Media context boundary handling: keeping runtime attachment paths usable while only exposing safe canonical locators in prompt-visible chat windows.

How is that risk mitigated?

Focused direct/group Telegram tests, cached-sticker media tests, auto-reply path canonicalization tests, TypeScript checks, formatting checks, git diff --check, and a clean local autoreview pass.

Current review state

What is the next action?

Maintainer review of the open PR.

What is still waiting on author, maintainer, CI, or external proof?

Waiting on maintainer review, CI, and any maintainer-requested live Telegram proof. Author-side local production-command proof and supplemental source/test proof are complete.

Which bot or reviewer comments were addressed?

Local autoreview findings were addressed before the original commit: chat-window media_path rendering support, unused sticker cache plumbing, group visibility for reply-chain media, raw local path prompt exposure, runtime attachment path preservation, untrusted media_path sanitization, and canonical URI double-encoding. PR #93130 CI feedback was addressed after opening: no-control-regex lint failures, the TS2556 test mock spread type error, and the Real behavior proof gate's request for non-test copied live output.