Skip to content

ChatClientAutoConfiguration should back off if there are multiple ChatModels #3429

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

filiphr
Copy link
Contributor

@filiphr filiphr commented Jun 3, 2025

If for whatever reason I have multiple ChatModel beans available, the ChatClientAutoConfiguration is going to fail because no ChatClient.Builder can be created.

This PR adds the @ConditionalOnSingleCandidate for the chatClientBuilder bean, which allows for smooth startup without the need to manually exclude the ChatClientAutoConfiguration

@filiphr filiphr force-pushed the multiple-chat-clients branch from 3131e19 to 427ed57 Compare June 3, 2025 15:47
@filiphr
Copy link
Contributor Author

filiphr commented Jun 18, 2025

Just wanted to check whether the PR is OK or I need to do some additional changes for it

@filiphr filiphr force-pushed the multiple-chat-clients branch from 427ed57 to 218ab48 Compare July 18, 2025 13:54
@ilayaperumalg
Copy link
Member

@filiphr Thanks for the PR! Linking the PR #3172 as it tries to fix the same issue.

@filiphr
Copy link
Contributor Author

filiphr commented Jul 21, 2025

Thanks @ilayaperumalg, I didn't see that PR. They are indeed trying to fix the same issue. Looking forward to either one getting resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants