feat: support multiple providers #311

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.

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

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.

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

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

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

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.

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

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.

kyteinsky · 2026-01-13T10:34:42Z

lib/Service/OpenAiAPIService.php

+		if ($serviceType === Application::SERVICE_TYPE_IMAGE) {
+			$serviceUrl = $this->openAiSettingsService->getImageUrl();
+		} elseif ($serviceType === Application::SERVICE_TYPE_STT) {
+			$serviceUrl = $this->openAiSettingsService->getSttUrl();
+		} elseif ($serviceType === Application::SERVICE_TYPE_TTS) {
+			$serviceUrl = $this->openAiSettingsService->getTtsUrl();
+		}


maybe getImageServiceUrl would better explain the function, and so on for others

kyteinsky · 2026-01-13T13:22:07Z

lib/Service/OpenAiAPIService.php

 			if ($this->modelsMemoryCache !== null) {
 				$this->logger->debug('Getting OpenAI models from the memory cache');
 				return $this->modelsMemoryCache;
 			}


this cache needs to be aligned with serviceType too, otherwise $serviceType = null's models are returned for every serviceType leading to an invalid list of models in the assistant modal if one of the services is overridden with non-intersecting models list

kyteinsky · 2026-01-13T13:38:48Z

lib/Service/OpenAiAPIService.php

+			if ($serviceType === Application::SERVICE_TYPE_IMAGE) {
+				$serviceUrl = $this->openAiSettingsService->getImageUrl();


let's maybe check for each service type if the override service url is set/not empty and only then apply overrides
right now it feels like for any image request, we're setting all the override image settings first only to later discover the image's service url was empty and then re-set all the values

ah imageOverrideEnabled() is already added for this

kyteinsky · 2026-01-13T13:39:51Z

lib/Service/OpenAiAPIService.php


-			$timeout = $this->openAiSettingsService->getRequestTimeout();
+			// Currently only supporting user api keys for the default service
+			if (empty($serviceUrl)) {


after the above change, this can be just else

kyteinsky · 2026-01-13T13:49:38Z

lib/Service/OpenAiAPIService.php

-		if ($this->isUsingOpenAi()) {
+		if ($this->isUsingOpenAi() || $this->openAiSettingsService->imageOverrideEnabled()) {


maybe it's more likely that it would be available when it's been overridden but we can't be sure
same for others

kyteinsky · 2026-01-13T14:57:43Z

src/components/AdminSettings.vue

+						label: m.id
+									+ (m.owned_by ? ' (' + m.owned_by + ')' : ''),


Suggested change

label: m.id

+ (m.owned_by ? ' (' + m.owned_by + ')' : ''),

label: m.id

+ (m.owned_by ? ' (' + m.owned_by + ')' : ''),

kyteinsky · 2026-01-14T07:16:33Z

src/components/AdminSettings.vue

 		},
+		async getAllModels(shouldSave = true) {
+			const models = this.getModels() // for text
+			console.error(this.models)


Suggested change

console.error(this.models)

console.debug(this.models)

kyteinsky · 2026-01-14T07:35:46Z

src/components/AdminSettings.vue

 			})
 		},
+		async getAllModels(shouldSave = true) {
+			const models = this.getModels() // for text


some indication that models is a Promise would be nice

kyteinsky · 2026-01-14T07:39:17Z

src/components/AdminSettings.vue

+					|| this.state.default_completion_model_id !== this.selectedModel.text.id
+					|| this.state.default_image_model_id !== this.selectedModel.image.id) {


checks for stt and tts too

kyteinsky · 2026-01-14T08:05:49Z

src/components/ServiceOverridePanel.vue

maybe some indication if a service is overridden would be cool, maybe a big blue dot or something beside the override button

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

feat: support multiple providers

87aaffa

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

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

clean up getModels and fix bug

0959036

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

julien-nc reviewed Jan 8, 2026

View reviewed changes

lukasdotcom force-pushed the feat/multiple-providers branch from 646c2e0 to dba53a3 Compare January 9, 2026 18:25

Add override sections for each individually

826cbbf

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

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

Constants for service types

f9404fe

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

julien-nc approved these changes Jan 12, 2026

View reviewed changes

kyteinsky requested changes Jan 14, 2026

View reviewed changes

		if ($serviceType === Application::SERVICE_TYPE_IMAGE) {
		$serviceUrl = $this->openAiSettingsService->getImageUrl();

		if ($this->isUsingOpenAi()) {
		if ($this->isUsingOpenAi() \|\| $this->openAiSettingsService->imageOverrideEnabled()) {

		\|\| this.state.default_completion_model_id !== this.selectedModel.text.id
		\|\| this.state.default_image_model_id !== this.selectedModel.image.id) {

feat: support multiple providers #311

Are you sure you want to change the base?

feat: support multiple providers #311

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!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

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!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

lukasdotcom commented Dec 15, 2025 •

edited

Loading

julien-nc left a comment •

edited

Loading

kyteinsky commented Jan 8, 2026 •

edited

Loading