Markdown 中的远程图片会触发自动网络下载并重新上传到飞书
原文依据:6 处发送或回复 Markdown 时,CLI 会自动访问其中的 http/https 图片 URL,再把响应内容上传到飞书。若 Markdown 来自转发的文档或不可信消息,单次“发送这段内容”的批准可能同时授权了用户没有注意到的外部请求和文件复制。所示材料未说明私网地址阻断或域名允许列表。
外部站点可获知请求时间和运行环境网络地址;若运行环境可访问内部 URL,返回内容还可能被复制到飞书消息中。失败只会移除图片并警告,可能不易被收件人察觉。
发送或回复 Markdown 时,远程图片 URL 会被 CLI 下载,再上传到飞书;这确实增加了对外网络请求和内容复制。虽然发送前要求确认收件人、内容和身份,但材料未显示会单独确认远程抓取,也未说明私网地址阻断或域名白名单。用户可要求禁用远程图片解析、先预览 URL,或仅允许已上传的 `img_xxx`。
The shortcut does all of the following before sending:1. Forces `msg_type=post`2. Resolves remote Markdown images like `` by downloading and uploading them first3. Normalizes the Markdown for Feishu post rendering4. Wraps the result as:查看另外 5 个位置
- Local paths in Markdown image syntax like `` are **not** supported and will not be auto-uploaded.- Remote URLs (`https://...`) will be auto-downloaded and uploaded at runtime; if the download or upload fails, the image is removed with a warning.- Media flags accept an existing key (`img_xxx` / `file_xxx`), an `http://` or `https://` URL, or a local file path.- Local paths must be relative to the current working directory and stay within it after resolving `..` and symlinks.- Absolute paths such as `/tmp/photo.png` are rejected. Run the command from the file's directory and pass `./photo.png`, or copy the file into the current directory first.- `--audio` sends a voice message and accepts only Opus audio (`.opus` or Ogg Opus `.ogg`) for local paths and URLs. For `mp3`, `wav`, or other non-Opus audio, convert to `.opus` before using `--audio`, or use `--file` to send the original audio as an attachment.When sending content fetched from a Lark doc as a message, fetch the doc with --doc-format im-markdown, then send it as a message using the --markdown format. The fetched content is already in markdown; in any content-forwarding scenario, keep the fetched original text and send it in the --markdown format. Note: if the doc contains a cite tag with type="user", keep it as-is and do not strip the tag.Messages sent by this tool are visible to other people. Before calling it, you **must** confirm with the user:1. The recipient (which person or which group)2. The message content3. The sending identity (user or bot)**Do not** send messages without explicit user approval.- Excess blank lines are compressed.- Already-uploaded `img_xxx` image keys are the most reliable Markdown image input.- Local paths in Markdown image syntax like `` are **not** supported and will not be auto-uploaded.- Remote URLs (`https://...`) will be auto-downloaded and uploaded at runtime; if the download or upload fails, the image is removed with a warning.