openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@f0b327cf68

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-27 10:29:59 +00:00
parent 0e78a6c192
commit 5a601cd562
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -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"
}

4
docs/reference/rich-output-protocol.md
View File

@ -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.