mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
Request to Add "Doubao-embedding-vision" to Volcano Engine's Text Embedding Models #783
Reference in New Issue
Block a user
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?
Originally created by @jiachenglin-creator on GitHub (Nov 6, 2025).
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
I’ve been working on tasks that involve embedding text content associated with visual information—like captions for images, product descriptions with visual details, or mixed media texts that reference visual elements. To handle these, I tried using the Volcano Engine provider in Dify, specifically selecting the "Text Embedding" feature to generate embeddings that could better align with both textual and underlying visual contexts.
However, when I accessed the model options under Volcano Engine’s Text Embedding, I found only "Doubao-embedding" and "Doubao-embedding-large" available. The "Doubao-embedding-vision" model, which I understand is designed to handle text with visual associations more effectively, is missing from the list.
This was frustrating because it forced me to use less suitable models that don’t account for the visual components in my text, leading to less accurate embeddings. It disrupted my workflow, as I had to either compromise on results or find workaround tools outside Dify to get the job done. Having "Doubao-embedding-vision" available would make Dify a one-stop solution for my mixed text-visual embedding needs with Volcano Engine.
2. Additional context or comments
No response
3. Can you help us with this feature?
@jiachenglin-creator commented on GitHub (Nov 6, 2025):
@dosubot[bot] commented on GitHub (Nov 22, 2025):
Hi, @jiachenglin-creator. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!