feat: support multiple providers by lukasdotcom · Pull Request #311 · nextcloud/integration_openai

lukasdotcom · 2025-12-15T16:05:57Z

Simple Overview
Adds hidden menus for override in the ui. When you select a different context you can specify settings for that context otherwise the default will be used.

Description

Creates preferences that allow for an override for all the connection settings for image, tts, and stt. These are used whenever the url is set for one of them. You'll see all the setters and getters for that in the OpenAiSettingsService. Also made sure to use the correct information in the OpenAiAPIService and do caching for each separate context for getModels.
Allow in the admin settings to set an override for image, tts, stt. The settings are hidden in 3 different submenus that use the new ServiceOverridePanel Component. Then changed the getModels endpoint to store the model list in 3 separate lists models, imageModels, sttModels, and ttsModels. Also added a lot of computed values for each of the settings that can be different depending on the context.

julien-nc

Could you describe more what the change actually is? It would make it easier to navigate in the diff.
After switching to this branch and reloading the settings, i get

Is it expected?

It is not clear what is specific to the selected context and what is global. It might help to group what is context-specific or add an indicator next to each of those fields.
Maybe it's more explicit or easy to follow for the users if there are 4 "service" blocks: a global one, one for image gen, one for tts, one for stt. Each block would be placed in the related section.

lukasdotcom · 2026-01-07T18:29:19Z

Could you describe more what the change actually is? It would make it easier to navigate in the diff.

After switching to this branch and reloading the settings, i get

Is it expected?
* It is not clear what is specific to the selected context and what is global. It might help to group what is context-specific or add an indicator next to each of those fields.

* Maybe it's more explicit or easy to follow for the users if there are 4 "service" blocks: a global one, one for image gen, one for tts, one for stt. Each block would be placed in the related section.

I updated the description with some more detailed information.
The screenshot shows a bug that got through it shouldn't show that. I pushed a fix for that.
The settings that are specific to each selected context are everything until you reach Text Generation.
Having 4 service blocks was the other option I had been debating, but the settings are already long and I didn't want to make them even larger specifically because there are probably a lot of users that wouldn't touch all of the settings. I do think there should definitely be some indication on what settings change based on context though.

kyteinsky · 2026-01-08T08:43:47Z

Agree with Julien, it doesn't come naturally how the settings would be affected after the dropdown is changed.
maybe it would be better to make the other sections disappear. When the dropdown is for images for example, the text2text, text2speech and speech2text sections are hidden.
Julien's solution might still be more convenient to reason about when there is a global setting and each block has an override option to add the specific api url and auth for that service, they could be collapsibles too so the settings don't look too long.
although unfortunately we don't have a collapsible widget yet in the nc/vue library afaict.
in app_api, there is a similar component, which is just a button that toggles the v-if of the div below.

julien-nc

I think we still need to clarify what is impacted by switching contexts. Either a visual clue of an explanation text in a note card.
We should mention that text generation is necessarily configured with the default context.

julien-nc · 2026-01-08T16:48:52Z

lib/Service/OpenAiAPIService.php

 		} else {
 			$serviceName = $this->openAiSettingsService->getServiceName();
+			if ($serviceType === 'image' && $this->openAiSettingsService->imageOverrideEnabled()) {
+				$serviceName = $this->openAiSettingsService->getImageServiceName();


If it's an override (the override URL is defined) it does not mean the service name is defined. We should probably fall back to the default one. Wdyt?

I'm not sure. It does fallback to LocalAI if a service name isn't defined and I think that is a better default than the service name of the text processing provider.

Ok then let's change the fallback. Instead of LocalAI it could be something more generic like OpenAI/LocalAI integration.

It does detect OpenAI automatically, so OpenAI/LocalAI probably isn't the best name. I can't think of a better one though.

lib/Service/OpenAiAPIService.php

lukasdotcom · 2026-01-09T18:34:09Z

Agree with Julien, it doesn't come naturally how the settings would be affected after the dropdown is changed. maybe it would be better to make the other sections disappear. When the dropdown is for images for example, the text2text, text2speech and speech2text sections are hidden. Julien's solution might still be more convenient to reason about when there is a global setting and each block has an override option to add the specific api url and auth for that service, they could be collapsibles too so the settings don't look too long. although unfortunately we don't have a collapsible widget yet in the nc/vue library afaict. in app_api, there is a similar component, which is just a button that toggles the v-if of the div below.

I like the collapsible idea and made an implementation using that. There are now collapsible portions that contain the settings for each. Here is what it looks like for the image portion. I also added an outline to make it clear what settings are changed by this like Julien had said.

julien-nc

This is much better visually and logically 👍

Small change suggestion, otherwise let's go.

julien-nc · 2026-01-12T15:40:46Z

lib/Service/OpenAiAPIService.php

 		} else {
 			$serviceName = $this->openAiSettingsService->getServiceName();
+			if ($serviceType === 'image' && $this->openAiSettingsService->imageOverrideEnabled()) {
+				$serviceName = $this->openAiSettingsService->getImageServiceName();


Ok then let's change the fallback. Instead of LocalAI it could be something more generic like OpenAI/LocalAI integration.

lib/Service/OpenAiAPIService.php

src/components/AdminSettings.vue

src/components/ServiceOverridePanel.vue

kyteinsky

🚀

Signed-off-by: Lukas Schaefer <lukas@lschaefer.xyz>

Signed-off-by: Julien Veyssier <julien-nc@posteo.net>

lukasdotcom marked this pull request as draft December 15, 2025 17:10

lukasdotcom force-pushed the feat/multiple-providers branch 6 times, most recently from 0a16060 to ec9f3f6 Compare December 17, 2025 14:42

lukasdotcom marked this pull request as ready for review December 17, 2025 14:42

lukasdotcom requested review from julien-nc and kyteinsky December 17, 2025 14:43

lukasdotcom force-pushed the feat/multiple-providers branch from ec9f3f6 to 87aaffa Compare January 7, 2026 15:25

julien-nc reviewed Jan 7, 2026

View reviewed changes

julien-nc reviewed Jan 8, 2026

View reviewed changes

lukasdotcom force-pushed the feat/multiple-providers branch 2 times, most recently from dba53a3 to 826cbbf Compare January 9, 2026 18:29

julien-nc approved these changes Jan 12, 2026

View reviewed changes

kyteinsky requested changes Jan 14, 2026

View reviewed changes

kyteinsky approved these changes Jan 15, 2026

View reviewed changes

lukasdotcom and others added 6 commits January 16, 2026 12:15

feat: support multiple providers

897ee72

Signed-off-by: Lukas Schaefer <lukas@lschaefer.xyz>

clean up getModels and fix bug

4a678ce

Signed-off-by: Lukas Schaefer <lukas@lschaefer.xyz>

Add override sections for each individually

0126bd3

Signed-off-by: Lukas Schaefer <lukas@lschaefer.xyz>

Constants for service types

f82b143

Signed-off-by: Lukas Schaefer <lukas@lschaefer.xyz>

fixes for reviews

aaff002

Signed-off-by: Lukas Schaefer <lukas@lschaefer.xyz>

fix: run cs:fix

845e910

Signed-off-by: Julien Veyssier <julien-nc@posteo.net>

julien-nc force-pushed the feat/multiple-providers branch from dc0ded3 to 845e910 Compare January 16, 2026 11:19

julien-nc merged commit 2b5fbd8 into main Jan 16, 2026
27 checks passed

julien-nc deleted the feat/multiple-providers branch January 16, 2026 11:34

This was referenced Jan 16, 2026

Prepare 4.2.0 #327

Merged

Fix 4.2.0 preparation #328

Merged

Conversation

lukasdotcom commented Dec 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

julien-nc left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lukasdotcom commented Jan 7, 2026

Uh oh!

kyteinsky commented Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

julien-nc left a comment

Choose a reason for hiding this comment

Uh oh!

julien-nc Jan 8, 2026

Choose a reason for hiding this comment

Uh oh!

lukasdotcom Jan 9, 2026

Choose a reason for hiding this comment

Uh oh!

julien-nc Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

lukasdotcom Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

lukasdotcom commented Jan 9, 2026

Uh oh!

julien-nc left a comment

Choose a reason for hiding this comment

Uh oh!

julien-nc Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

kyteinsky left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

lukasdotcom commented Dec 15, 2025 •

edited

Loading

julien-nc left a comment •

edited

Loading

kyteinsky commented Jan 8, 2026 •

edited

Loading