mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
After selecting the official agent for the agent strategy in chatflow, the Tongyi large model is not fully displayed #642
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 @zt89974292 on GitHub (Sep 11, 2025).
Self Checks
Dify version
1.8.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
It can be seen that there is a deepseek-v3 model in the backend interface, but it is not present when selecting the agent
✔️ Expected Behavior
The official agent strategy can display all models normally
❌ Actual Behavior
No response
@crazywoola commented on GitHub (Sep 11, 2025):
https://github.com/langgenius/dify-official-plugins/blob/5b74c3a1de4eeabe220687759b5de73436fe9495/models/cometapi/models/llm/deepseek/deepseek-v3.yaml#L6
It lacks the support of these parameters
https://github.com/langgenius/dify-official-plugins/blob/5b74c3a1de4eeabe220687759b5de73436fe9495/models/cometapi/models/llm/deepseek/deepseek-r1-0528.yaml#L6-L9
Issues related to plugins should use this template https://github.com/langgenius/dify-official-plugins/issues/new?template=bug_report.yml
@dosubot[bot] commented on GitHub (Sep 11, 2025):
Hi @zt89974292! I'm Dosu and I’m helping the dify-official-plugins team.
The Tongyi large model and DeepSeek-v3 may not appear in the agent selection because only models that support tool-calling (function call or ReACT) are shown in the Agent node. DeepSeek is a built-in provider, not a plugin-based one, so it won't be listed unless it supports these capabilities. For Tongyi, there are known compatibility issues—especially if the plugin is missing required fields like
descriptionor is not fully compatible with MCP. Upgrading or downgrading the Tongyi plugin, reinstalling it from the Dify Marketplace, and ensuring it was initialized with full network access can resolve display issues. Also, make sure your plugin version is up to date and that your Docker environment allows the plugin to install dependencies during setup. Refreshing the page after adding new models can sometimes help them appear in the dropdown as well. More details and troubleshooting steps are available here and here.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
