langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 20:45:26 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Chat UI: render image URLs/attachments inline (e.g. QR code) instead of plain link #22113

New Issue
Open
opened 2026-02-21 20:15:49 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 20:15:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @farmer878 on GitHub (Feb 5, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Scenario
I built a Dify chatbot workflow that generates a QR code for an activity. The workflow returns a public HTTPS URL pointing to a PNG (QR code image).
In the chat UI, the assistant message shows the URL as plain text only. Users must click the link to view the QR code, which breaks the conversational UX.

Expected behavior
If the assistant output contains:

  • a direct image URL (png/jpg/...)
  • Markdown image syntax like ![](https://...)
  • an attachment/file object with mime_type starting with image/

the chat UI should render an inline image preview

Actual behavior
Only the URL text is rendered (no inline preview), even when the URL is a valid image and can be opened in the browser.

2. Additional context or comments

Steps to reproduce

  1. Create a workflow that generates an image output (e.g., a QR code PNG) via a tool(MCP).
  2. Trigger the workflow from the Chat UI.
  3. Observe the assistant output: the UI shows only a URL link instead of rendering the image inline.
  4. Click the URL to confirm it points to a valid image file.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @farmer878 on GitHub (Feb 5, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. **Scenario** I built a Dify chatbot workflow that generates a QR code for an activity. The workflow returns a public HTTPS URL pointing to a PNG (QR code image). In the chat UI, the assistant message shows the URL as plain text only. Users must click the link to view the QR code, which breaks the conversational UX. **Expected behavior** If the assistant output contains: - a direct image URL (png/jpg/...) - Markdown image syntax like `![](https://...)` - an attachment/file object with `mime_type` starting with `image/` the chat UI should render an inline image preview **Actual behavior** Only the URL text is rendered (no inline preview), even when the URL is a valid image and can be opened in the browser. ### 2. Additional context or comments **Steps to reproduce** 1. Create a workflow that generates an image output (e.g., a QR code PNG) via a tool(MCP). 2. Trigger the workflow from the Chat UI. 3. Observe the assistant output: the UI shows only a URL link instead of rendering the image inline. 4. Click the URL to confirm it points to a valid image file. ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 20:15:49 -05:00
yindo commented 2026-02-21 20:15:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 5, 2026):

Hi @farmer878! I'm Dosu and I’m helping the dify team.

Dify's chat UI currently renders images inline only if they are provided as Markdown image syntax (like ![](https://...)) or as attachments with the correct mime_type metadata (e.g., image/png). Plain image URLs (such as direct links ending in .png, .jpg, etc.) are not auto-rendered as images—they appear as clickable links instead. This is a known limitation and is tracked as an open feature request for improvement "render image URLs/attachments inline".

The frontend is built with React. Chat messages are rendered by components like Answer and BasicContent, which delegate to a Markdown renderer. This renderer supports Markdown image syntax and renders images using an Img component, but does not auto-detect plain image URLs in text. Attachments are handled by the FileList and FileImageItem components, which display image files inline if the backend provides the correct metadata.

To implement inline rendering for plain image URLs, you could extend the Markdown rendering pipeline or preprocess chat content to convert detected image URLs into Markdown image syntax before rendering. The most relevant files for this work are:

  • web/app/components/base/chat/chat/answer/basic-content.tsx
  • web/app/components/base/markdown/index.tsx
  • web/app/components/base/markdown/react-markdown-wrapper.tsx
  • web/app/components/base/markdown-blocks/img.tsx
  • web/app/components/base/file-uploader/file-uploader-in-chat-input/file-list.tsx
  • web/app/components/base/file-uploader/file-uploader-in-chat-input/file-image-item.tsx

For attachments, make sure the backend includes the correct mime_type (e.g., image/png) in the file metadata so the frontend can render them inline. For Markdown, ensure image references are serialized as Markdown, not just as plain URLs or HTML tags, since raw HTML is not supported for security reasons "chat UI only displays images if the image URLs are included in the message content using markdown image syntax".

If you want to contribute, focus on adding logic to detect image URLs in plain text and convert them to Markdown image syntax before passing them to the Markdown renderer. This would close the gap and provide the inline image preview experience you're looking for.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 5, 2026): <!-- Greeting --> Hi @farmer878! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> Dify's chat UI currently renders images inline only if they are provided as Markdown image syntax (like `![](https://...)`) or as attachments with the correct `mime_type` metadata (e.g., `image/png`). Plain image URLs (such as direct links ending in `.png`, `.jpg`, etc.) are not auto-rendered as images—they appear as clickable links instead. This is a known limitation and is tracked as an open feature request for improvement ["render image URLs/attachments inline"](https://github.com/langgenius/dify/issues/32031). The frontend is built with React. Chat messages are rendered by components like `Answer` and `BasicContent`, which delegate to a Markdown renderer. This renderer supports Markdown image syntax and renders images using an `Img` component, but does not auto-detect plain image URLs in text. Attachments are handled by the `FileList` and `FileImageItem` components, which display image files inline if the backend provides the correct metadata. To implement inline rendering for plain image URLs, you could extend the Markdown rendering pipeline or preprocess chat content to convert detected image URLs into Markdown image syntax before rendering. The most relevant files for this work are: - `web/app/components/base/chat/chat/answer/basic-content.tsx` - `web/app/components/base/markdown/index.tsx` - `web/app/components/base/markdown/react-markdown-wrapper.tsx` - `web/app/components/base/markdown-blocks/img.tsx` - `web/app/components/base/file-uploader/file-uploader-in-chat-input/file-list.tsx` - `web/app/components/base/file-uploader/file-uploader-in-chat-input/file-image-item.tsx` For attachments, make sure the backend includes the correct `mime_type` (e.g., `image/png`) in the file metadata so the frontend can render them inline. For Markdown, ensure image references are serialized as Markdown, not just as plain URLs or HTML tags, since raw HTML is not supported for security reasons ["chat UI only displays images if the image URLs are included in the message content using markdown image syntax"](https://github.com/langgenius/dify/discussions/27300). If you want to contribute, focus on adding logic to detect image URLs in plain text and convert them to Markdown image syntax before passing them to the Markdown renderer. This would close the gap and provide the inline image preview experience you're looking for. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/a764a2be-9bac-4fad-9d2c-3e819d79fc4b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a764a2be-9bac-4fad-9d2c-3e819d79fc4b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a764a2be-9bac-4fad-9d2c-3e819d79fc4b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a764a2be-9bac-4fad-9d2c-3e819d79fc4b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a764a2be-9bac-4fad-9d2c-3e819d79fc4b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a764a2be-9bac-4fad-9d2c-3e819d79fc4b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a764a2be-9bac-4fad-9d2c-3e819d79fc4b?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Dify%27s%20chat%20UI%20currently%20renders%20images%20inline%20only%20if%20they%20are%20provided%20as%20Markdown%20image%20syntax%20%28like%20%60%21%5B%5D%28https%3A//...%29%60%29%20or%20as%20attachments%20with%20the%20correct%20%60mime_type%60%20metadata%20%28e.g.%2C%20%60image/png%60%29.%20Plain%20image%20URLs%20%28such%20as%20direct%20links%20ending%20in%20%60.png%60%2C%20%60.jpg%60%2C%20etc.%29%20are%20not%20auto-rendered%20as%20images%E2%80%94they%20appear%20as%20clickable%20links%20instead.%20This%20is%20a%20known%20limitation%20and%20is%20tracked%20as%20an%20open%20feature%20request%20for%20improvement%20%5B%22render%20image%20URLs/attachments%20inline%22%5D%28https%3A//github.com/langgenius/dify/issues/32031%29.%0A%0AThe%20frontend%20is%20built%20with%20React.%20Chat%20messages%20are%20rendered%20by%20components%20like%20%60Answer%60%20and%20%60BasicContent%60%2C%20which%20delegate%20to%20a%20Markdown%20renderer.%20This%20renderer%20supports%20Markdown%20image%20syntax%20and%20renders%20images%20using%20an%20%60Img%60%20component%2C%20but%20does%20not%20auto-detect%20plain%20image%20URLs%20in%20text.%20Attachments%20are%20handled%20by%20the%20%60FileList%60%20and%20%60FileImageItem%60%20components%2C%20which%20display%20image%20files%20inline%20if%20the%20backend%20provides%20the%20correct%20metadata.%0A%0ATo%20implement%20inline%20rendering%20for%20plain%20image%20URLs%2C%20you%20could%20extend%20the%20Markdown%20rendering%20pipeline%20or%20preprocess%20chat%20content%20to%20convert%20detected%20image%20URLs%20into%20Markdown%20image%20syntax%20before%20rendering.%20The%20most%20relevant%20files%20for%20this%20work%20are%3A%0A%0A-%20%60web/app/components/base/chat/chat/answer/basic-content.tsx%60%0A-%20%60web/app/components/base/markdown/index.tsx%60%0A-%20%60web/app/components/base/markdown/react-markdown-wrapper.tsx%60%0A-%20%60web/app/components/base/markdown-blocks/img.tsx%60%0A-%20%60web/app/components/base/file-uploader/file-uploader-in-chat-input/file-list.tsx%60%0A-%20%60web/app/components/base/file-uploader/file-uploader-in-chat-input/file-image-item.tsx%60%0A%0AFor%20attachments%2C%20make%20sure%20the%20backend%20includes%20the%20correct%20%60mime_type%60%20%28e.g.%2C%20%60image/png%60%29%20in%20the%20file%20metadata%20so%20the%20frontend%20can%20render%20them%20inline.%20For%20Markdown%2C%20ensure%20image%20references%20are%20serialized%20as%20Markdown%2C%20not%20just%20as%20plain%20URLs%20or%20HTML%20tags%2C%20since%20raw%20HTML%20is%20not%20supported%20for%20security%20reasons%20%5B%22chat%20UI%20only%20displays%20images%20if%20the%20image%20URLs%20are%20included%20in%20the%20message%20content%20using%20markdown%20image%20syntax%22%5D%28https%3A//github.com/langgenius/dify/discussions/27300%29.%0A%0AIf%20you%20want%20to%20contribute%2C%20focus%20on%20adding%20logic%20to%20detect%20image%20URLs%20in%20plain%20text%20and%20convert%20them%20to%20Markdown%20image%20syntax%20before%20passing%20them%20to%20the%20Markdown%20renderer.%20This%20would%20close%20the%20gap%20and%20provide%20the%20inline%20image%20preview%20experience%20you%27re%20looking%20for.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/32031)
yindo commented 2026-02-21 20:15:50 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 5, 2026):

I suggest that you can instruct the Agent to render with markdown syntax.

@crazywoola commented on GitHub (Feb 5, 2026): I suggest that you can instruct the Agent to render with markdown syntax.
yindo commented 2026-02-21 20:15:50 -05:00
Author
Owner
Copy Link
Copy Source

@shuangqingqiang commented on GitHub (Feb 6, 2026):

安全积分超市活动二维码已成功生成！

活动详情：

活动名称：安全积分测试活动
可兑换数量：20 件
每次兑换积分：5 分
您可以使用手机扫描二维码参与活动，或者点击以下链接查看二维码图片： if mcp function return this work ？ @dosu

Image
@shuangqingqiang commented on GitHub (Feb 6, 2026): 安全积分超市活动二维码已成功生成！ 活动详情： 活动名称：安全积分测试活动 可兑换数量：20 件 每次兑换积分：5 分 您可以使用手机扫描二维码参与活动，或者点击以下链接查看二维码图片： ![](https://wlys.cr11g.com.cn/worker/api/business/file/download?bucketName=labor-register&filePath=activity_qrcode/activity_qrcode_2019595305427767298.png) if mcp function return this work ？ @dosu <img width="1115" height="550" alt="Image" src="https://github.com/user-attachments/assets/80287d1e-f9e1-4f91-8472-2b5cfb2c9d2c" />
yindo commented 2026-02-21 20:15:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 6, 2026):

MCP 函数返回 <image ... /> 这种自定义 HTML 标签，Dify 聊天界面不会将其渲染为图片，只会显示为普通文本或占位符。当前支持的图片内联渲染方式有两种：

  1. 用 Markdown 图片语法，例如 ![](https://your-image-url.png)，这样图片会直接在聊天界面内联显示 参考。
  2. 作为附件返回，并在元数据（meta）里带上正确的 mime_type（如 image/png），这样前端会自动识别为图片并渲染 参考。

如果你希望二维码直接显示，建议让 MCP 函数输出 Markdown 图片语法，或者作为带有 mime_type 的附件返回图片链接。自定义 <image> 标签不会被识别和渲染 参考。

如需进一步扩展支持自动识别纯图片链接或自定义标签，需要修改前端 Markdown 渲染逻辑（如 react-markdown-wrapper.tsx），目前官方未实现此功能。

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 6, 2026): <!-- Answer --> MCP 函数返回 `<image ... />` 这种自定义 HTML 标签，Dify 聊天界面不会将其渲染为图片，只会显示为普通文本或占位符。当前支持的图片内联渲染方式有两种： 1. 用 Markdown 图片语法，例如 `![](https://your-image-url.png)`，这样图片会直接在聊天界面内联显示 [参考](https://github.com/langgenius/dify/discussions/27300)。 2. 作为附件返回，并在元数据（meta）里带上正确的 `mime_type`（如 `image/png`），这样前端会自动识别为图片并渲染 [参考](https://github.com/langgenius/dify/issues/29654)。 如果你希望二维码直接显示，建议让 MCP 函数输出 Markdown 图片语法，或者作为带有 `mime_type` 的附件返回图片链接。自定义 `<image>` 标签不会被识别和渲染 [参考](https://github.com/langgenius/dify/discussions/27300)。 如需进一步扩展支持自动识别纯图片链接或自定义标签，需要修改前端 Markdown 渲染逻辑（如 `react-markdown-wrapper.tsx`），目前官方未实现此功能。 <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/4cc31555-0cd3-4744-ad37-265634cb51c1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/4cc31555-0cd3-4744-ad37-265634cb51c1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/4cc31555-0cd3-4744-ad37-265634cb51c1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/4cc31555-0cd3-4744-ad37-265634cb51c1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4cc31555-0cd3-4744-ad37-265634cb51c1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/4cc31555-0cd3-4744-ad37-265634cb51c1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4cc31555-0cd3-4744-ad37-265634cb51c1?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=MCP%20%E5%87%BD%E6%95%B0%E8%BF%94%E5%9B%9E%20%60%3Cimage%20...%20/%3E%60%20%E8%BF%99%E7%A7%8D%E8%87%AA%E5%AE%9A%E4%B9%89%20HTML%20%E6%A0%87%E7%AD%BE%EF%BC%8CDify%20%E8%81%8A%E5%A4%A9%E7%95%8C%E9%9D%A2%E4%B8%8D%E4%BC%9A%E5%B0%86%E5%85%B6%E6%B8%B2%E6%9F%93%E4%B8%BA%E5%9B%BE%E7%89%87%EF%BC%8C%E5%8F%AA%E4%BC%9A%E6%98%BE%E7%A4%BA%E4%B8%BA%E6%99%AE%E9%80%9A%E6%96%87%E6%9C%AC%E6%88%96%E5%8D%A0%E4%BD%8D%E7%AC%A6%E3%80%82%E5%BD%93%E5%89%8D%E6%94%AF%E6%8C%81%E7%9A%84%E5%9B%BE%E7%89%87%E5%86%85%E8%81%94%E6%B8%B2%E6%9F%93%E6%96%B9%E5%BC%8F%E6%9C%89%E4%B8%A4%E7%A7%8D%EF%BC%9A%0A%0A1.%20%E7%94%A8%20Markdown%20%E5%9B%BE%E7%89%87%E8%AF%AD%E6%B3%95%EF%BC%8C%E4%BE%8B%E5%A6%82%20%60%21%5B%5D%28https%3A//your-image-url.png%29%60%EF%BC%8C%E8%BF%99%E6%A0%B7%E5%9B%BE%E7%89%87%E4%BC%9A%E7%9B%B4%E6%8E%A5%E5%9C%A8%E8%81%8A%E5%A4%A9%E7%95%8C%E9%9D%A2%E5%86%85%E8%81%94%E6%98%BE%E7%A4%BA%20%5B%E5%8F%82%E8%80%83%5D%28https%3A//github.com/langgenius/dify/discussions/27300%29%E3%80%82%0A2.%20%E4%BD%9C%E4%B8%BA%E9%99%84%E4%BB%B6%E8%BF%94%E5%9B%9E%EF%BC%8C%E5%B9%B6%E5%9C%A8%E5%85%83%E6%95%B0%E6%8D%AE%EF%BC%88meta%EF%BC%89%E9%87%8C%E5%B8%A6%E4%B8%8A%E6%AD%A3%E7%A1%AE%E7%9A%84%20%60mime_type%60%EF%BC%88%E5%A6%82%20%60image/png%60%EF%BC%89%EF%BC%8C%E8%BF%99%E6%A0%B7%E5%89%8D%E7%AB%AF%E4%BC%9A%E8%87%AA%E5%8A%A8%E8%AF%86%E5%88%AB%E4%B8%BA%E5%9B%BE%E7%89%87%E5%B9%B6%E6%B8%B2%E6%9F%93%20%5B%E5%8F%82%E8%80%83%5D%28https%3A//github.com/langgenius/dify/issues/29654%29%E3%80%82%0A%0A%E5%A6%82%E6%9E%9C%E4%BD%A0%E5%B8%8C%E6%9C%9B%E4%BA%8C%E7%BB%B4%E7%A0%81%E7%9B%B4%E6%8E%A5%E6%98%BE%E7%A4%BA%EF%BC%8C%E5%BB%BA%E8%AE%AE%E8%AE%A9%20MCP%20%E5%87%BD%E6%95%B0%E8%BE%93%E5%87%BA%20Markdown%20%E5%9B%BE%E7%89%87%E8%AF%AD%E6%B3%95%EF%BC%8C%E6%88%96%E8%80%85%E4%BD%9C%E4%B8%BA%E5%B8%A6%E6%9C%89%20%60mime_type%60%20%E7%9A%84%E9%99%84%E4%BB%B6%E8%BF%94%E5%9B%9E%E5%9B%BE%E7%89%87%E9%93%BE%E6%8E%A5%E3%80%82%E8%87%AA%E5%AE%9A%E4%B9%89%20%60%3Cimage%3E%60%20%E6%A0%87%E7%AD%BE%E4%B8%8D%E4%BC%9A%E8%A2%AB%E8%AF%86%E5%88%AB%E5%92%8C%E6%B8%B2%E6%9F%93%20%5B%E5%8F%82%E8%80%83%5D%28https%3A//github.com/langgenius/dify/discussions/27300%29%E3%80%82%0A%0A%E5%A6%82%E9%9C%80%E8%BF%9B%E4%B8%80%E6%AD%A5%E6%89%A9%E5%B1%95%E6%94%AF%E6%8C%81%E8%87%AA%E5%8A%A8%E8%AF%86%E5%88%AB%E7%BA%AF%E5%9B%BE%E7%89%87%E9%93%BE%E6%8E%A5%E6%88%96%E8%87%AA%E5%AE%9A%E4%B9%89%E6%A0%87%E7%AD%BE%EF%BC%8C%E9%9C%80%E8%A6%81%E4%BF%AE%E6%94%B9%E5%89%8D%E7%AB%AF%20Markdown%20%E6%B8%B2%E6%9F%93%E9%80%BB%E8%BE%91%EF%BC%88%E5%A6%82%20%60react-markdown-wrapper.tsx%60%EF%BC%89%EF%BC%8C%E7%9B%AE%E5%89%8D%E5%AE%98%E6%96%B9%E6%9C%AA%E5%AE%9E%E7%8E%B0%E6%AD%A4%E5%8A%9F%E8%83%BD%E3%80%82)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/32031)
yindo commented 2026-02-21 20:15:50 -05:00
Author
Owner
Copy Link
Copy Source

@shuangqingqiang commented on GitHub (Feb 10, 2026):

{"activityCode": ""✅ 安全积分超市活动二维码生成成功！\n\n活动详情：\n- 活动名称： 欢迎实习生\n- 可兑换数量： 10 件\n- 参与可兑换的积分： 10 分\n\n活动二维码：\n\n安全积分超市活动二维码\n\n请使用手机扫描上方二维码参与活动，或点击链接查看二维码图片。""} our mcp function return this why it does not embedding what should i do

Image Image

Image @dosu

@shuangqingqiang commented on GitHub (Feb 10, 2026): {"activityCode": "\"✅ **安全积分超市活动二维码生成成功！**\\n\\n**活动详情：**\\n- **活动名称：** 欢迎实习生\\n- **可兑换数量：** 10 件\\n- **参与可兑换的积分：** 10 分\\n\\n**活动二维码：**\\n\\n![安全积分超市活动二维码](https://wlys.cr11g.com.cn/worker/api/business/file/download?bucketName=labor-register&filePath=activity_qrcode/activity_qrcode_2021149953250820097.png&action=preview)\\n\\n请使用手机扫描上方二维码参与活动，或点击链接查看二维码图片。\""} our mcp function return this why it does not embedding what should i do <img width="1622" height="1026" alt="Image" src="https://github.com/user-attachments/assets/49fef9c7-2c1a-4d4e-9e6c-8a081320293b" /> <img width="2305" height="1354" alt="Image" src="https://github.com/user-attachments/assets/6202a486-7fdf-4f2c-a8a7-629ddd0e965f" /> <img width="1914" height="780" alt="Image" src="https://github.com/user-attachments/assets/7cdfa35c-97d4-46a9-85a2-28d584556338" /> @dosu
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#22113
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?