From 5a601cd562ee4788f4bc7be9bb1d5efc8eb5876d Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Mon, 27 Apr 2026 10:29:59 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@f0b327cf686e3a957fef8c94985ee6509953a3b7 --- .openclaw-sync/source.json | 4 ++-- docs/reference/rich-output-protocol.md | 4 ++++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 52943852d..9a1756366 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "775ed36c16c2a03fe137ac9a84960b3426319262", - "syncedAt": "2026-04-27T10:26:57.175Z" + "sha": "f0b327cf686e3a957fef8c94985ee6509953a3b7", + "syncedAt": "2026-04-27T10:28:36.945Z" } diff --git a/docs/reference/rich-output-protocol.md b/docs/reference/rich-output-protocol.md index c869dd200..f31dd569f 100644 --- a/docs/reference/rich-output-protocol.md +++ b/docs/reference/rich-output-protocol.md @@ -17,6 +17,10 @@ Remote `MEDIA:` attachments must be public `https:` URLs. Plain `http:`, loopback, link-local, private, and internal hostnames are ignored as attachment directives; server-side media fetchers still enforce their own network guards. +Plain Markdown image syntax stays text by default. Channels that intentionally +map Markdown image replies to media attachments opt in at their outbound +adapter; Telegram does this so `![alt](url)` can still become a media reply. + These directives are separate. `MEDIA:` and reply/voice tags remain delivery metadata; `[embed ...]` is the web-only rich render path. Trusted tool-result media uses the same `MEDIA:` / `[[audio_as_voice]]` parser before delivery, so text tool outputs can still mark an audio attachment as a voice note.