langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

add a feature to dynamically switch model in workflow #20227

New Issue
Closed
opened 2026-02-21 20:06:23 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:06:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @Colstuwjx on GitHub (Nov 10, 2025).

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.

This issue is similar to #23718 , the background is that we have a centralized prompt mgmt system, like Langfuse prompt mgmt did, and we've stored the model configurations and also prompt template content in git repo and support to commit versions for prompt version mgmt.

However, since the dify workflow didn't support to pass dynamic model parameters, we could ONLY fetch the prompt template content in the LLM/Agent node, I know there is workaround way to achieve the similar goal, hope the team could evaluate this kind of features and see if it's possible to support it.

Thanks.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Colstuwjx on GitHub (Nov 10, 2025). ### 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. This issue is similar to #23718 , the background is that we have a centralized prompt mgmt system, like [Langfuse prompt mgmt](https://langfuse.com/docs/prompt-management/overview) did, and we've stored the model configurations and also prompt template content in git repo and support to commit versions for prompt version mgmt. However, since the dify workflow didn't support to pass dynamic model parameters, we could ONLY fetch the prompt template content in the LLM/Agent node, I know there is workaround way to achieve the similar goal, hope the team could evaluate this kind of features and see if it's possible to support it. Thanks. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement🌊 feat:workflow labels 2026-02-21 20:06:23 -05:00
yindo closed this issue 2026-02-21 20:06:23 -05:00
yindo commented 2026-02-21 20:06:23 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 11, 2025):

Hi, @Colstuwjx. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested a feature to dynamically switch model parameters within the Dify workflow.
  • The goal is to integrate with centralized prompt management systems that store model configurations and templates in version-controlled repositories.
  • Currently, only prompt content can be fetched dynamically; dynamic model parameter passing is not supported yet.
  • There has been no further activity or discussion on this request since it was opened.

Next Steps:

  • Please let me know if this feature request is still relevant to your use case with the latest version of Dify by commenting on this issue.
  • If I do not hear back within 15 days, this issue will be automatically closed to keep the backlog manageable.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 11, 2025): Hi, @Colstuwjx. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested a feature to dynamically switch model parameters within the Dify workflow. - The goal is to integrate with centralized prompt management systems that store model configurations and templates in version-controlled repositories. - Currently, only prompt content can be fetched dynamically; dynamic model parameter passing is not supported yet. - There has been no further activity or discussion on this request since it was opened. **Next Steps:** - Please let me know if this feature request is still relevant to your use case with the latest version of Dify by commenting on this issue. - If I do not hear back within 15 days, this issue will be automatically closed to keep the backlog manageable. Thank you for your understanding and contribution!
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 🌊 feat:workflow 💪 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#20227
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?