@@ -21,6 +21,28 @@ Local `MEDIA:` attachments can use absolute paths, workspace-relative paths, or
2121home-relative `~/` paths. They still pass through the agent file-read policy and
2222media type checks before delivery.
232324+<Warning>
25+`MEDIA:` is parsed only as plain text. Wrapping the directive in Markdown
26+formatting (bold, inline code, fenced code) prevents the parser from
27+recognizing it, and the attachment is silently dropped from delivery.
28+29+Valid:
30+31+```text
32+MEDIA:/workspace/image.png
33+```
34+35+Invalid (parsed as prose, no attachment delivered):
36+37+```text
38+**MEDIA:/workspace/image.png**
39+`MEDIA:/workspace/image.png`
40+Here is your image: MEDIA:/workspace/image.png
41+```
42+43+Keep `MEDIA:` on its own line, in plain text, with no surrounding formatting.
44+</Warning>
45+2446Plain Markdown image syntax stays text by default. Channels that intentionally
2547map Markdown image replies to media attachments opt in at their outbound
2648adapter; Telegram does this so `` can still become a media reply.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。