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

Allow credential set choice during model selection #16420

New Issue
Closed
opened 2026-02-21 19:26:02 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:26:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Aug 25, 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.

With the upcoming release, it will be possible to have multiple Authorization keys for a model:

Image

It would be nice if the LLM model picker could show the aggregation of every possible model from all the setup keys (eg: on a key you enable GPT4, on another you enable GPT3+GPT5) when choosing a model you see GPT3+4+5 and after selecting a model, if it has multiple keys, it allows you to choose the key you want to use.

Otherwise, I fail to understand the use-case of that feature if it can only swap the key for every running model.
It's not like you can have "staging", "development", "production" keys.... The tenant is just one, and users that are running a workflow while "production" key is selected, will suddenly start running the same workflow with "staging" key.

ATM it feels like a dumbed-down version of Load Balancer, where you manually choose a new key ?

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 @DavideDelbianco on GitHub (Aug 25, 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. With the upcoming release, it will be possible to have multiple Authorization keys for a model: <img width="761" height="286" alt="Image" src="https://github.com/user-attachments/assets/332c1185-4ace-47e0-b58f-a96421abefc1" /> It would be nice if the LLM model picker could show the aggregation of every possible model from all the setup keys (eg: on a key you enable GPT4, on another you enable GPT3+GPT5) when choosing a model you see GPT3+4+5 and after selecting a model, if it has multiple keys, it allows you to choose the key you want to use. Otherwise, I fail to understand the use-case of that feature if it can only swap the key for every running model. It's not like you can have "staging", "development", "production" keys.... The tenant is just one, and users that are running a workflow while "production" key is selected, will suddenly start running the same workflow with "staging" key. ATM it feels like a dumbed-down version of Load Balancer, where you manually choose a new key ? ### 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 label 2026-02-21 19:26:02 -05:00
yindo closed this issue 2026-02-21 19:26:02 -05:00
yindo commented 2026-02-21 19:26:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 25, 2025):

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

Issue Summary:

  • You requested enhancing the model selection interface to aggregate models from multiple authorization keys.
  • The goal is to enable selecting a key per model for more practical multi-key support.
  • This would improve workflows like staging versus production by avoiding global key switching.
  • The feature aims to provide greater flexibility than manual load balancing.
  • There has been no activity or comments on this issue so far.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 25, 2025): Hi, @DavideDelbianco. 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 enhancing the model selection interface to aggregate models from multiple authorization keys. - The goal is to enable selecting a key per model for more practical multi-key support. - This would improve workflows like staging versus production by avoiding global key switching. - The feature aims to provide greater flexibility than manual load balancing. - There has been no activity or comments on this issue so far. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of Dify by commenting here. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:26:03 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Oct 8, 2025):

@dosu it is still a nice to have feature

@DavideDelbianco commented on GitHub (Oct 8, 2025): @dosu it is still a nice to have feature
yindo commented 2026-02-21 19:26:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 8, 2025):

@crazywoola The user @DavideDelbianco has confirmed that the feature request for enhancing the model selection interface with multi-key support is still a nice-to-have. Could you please assist with this issue?

@dosubot[bot] commented on GitHub (Oct 8, 2025): @crazywoola The user @DavideDelbianco has confirmed that the feature request for enhancing the model selection interface with multi-key support is still a nice-to-have. Could you please assist with this issue?
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#16420
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?