feat: add export/import for provider configurations by yudanmao123 · Pull Request #1450 · moeru-ai/airi

yudanmao123 · 2026-03-22T09:37:50Z

Adds exportProviderConfigs() and importProviderConfigs() functions to the providers store.

This allows users to export their provider configurations to a JSON file and import them later, useful during development when data gets purged.

Usage:

import { exportProviderConfigs, importProviderConfigs } from 
  @proj-airi/stage-ui/stores/providers

// Export
const configJson = exportProviderConfigs()

// Import
importProviderConfigs(configJson)

Closes #973

gemini-code-assist · 2026-03-22T09:38:59Z

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces functionality to export and import provider configurations within the application. This enhancement allows developers to easily save and restore their configurations, which is especially useful during development cycles where data loss may occur. The changes involve adding two new functions, exportProviderConfigs and importProviderConfigs, to the providers store.

Highlights

Export/Import Functionality: Introduces exportProviderConfigs() and importProviderConfigs() functions to the providers store, enabling users to save and restore their provider configurations.
Data Persistence: Addresses the need to persist provider configurations, particularly useful during development when data is frequently purged.
Usage: Provides example code snippets demonstrating how to export provider configurations to a JSON string and import them back into the application.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6cf8085caa

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-03-22T09:41:53Z

+  const providerIds = store.configuredChatProviders.map(p => p.id)
+  providerIds.forEach(id => {
+    config[id] = store.getProviderConfig(id) || {}


Export every persisted provider, not just configured chat ones

This loop only serializes chat providers that are currently marked configured. In the same store we already track configured speech/transcription providers (configuredSpeechProvidersMetadata, configuredTranscriptionProvidersMetadata at packages/stage-ui/src/stores/providers.ts:2158-2168) and persisted-but-not-yet-configured entries via shouldListProvider() (packages/stage-ui/src/stores/providers.ts:2179-2184). As a result, backing up a setup with TTS/STT providers or a chat provider that is temporarily failing validation/manual testing will silently omit those credentials, so the subsequent import cannot restore the user's full provider setup.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-03-22T09:41:53Z

+    Object.entries(config).forEach(([providerId, providerConfig]) => {
+      store.setProviderConfig(providerId, providerConfig)


Preserve added-provider state during import

importProviderConfigs() restores only the credential object, but visibility is gated by addedProviders or a non-default config (shouldListProvider() in packages/stage-ui/src/stores/providers.ts:2179-2184). That is why useProviderValidation() explicitly calls markProviderAdded() for valid providers such as LM Studio whose working config can exactly match the defaults (packages/stage-ui/src/composables/use-provider-validation.ts:83-89). After exporting and re-importing one of those providers, the credentials come back but addedProviders stays empty, so the provider disappears from selectors/settings until the user opens the page and revalidates it manually.

Useful? React with 👍 / 👎.

gemini-code-assist

Code Review

This pull request adds functionality to export and import provider configurations. There are a couple of issues in the implementation. The exportProviderConfigs function attempts to access a non-existent property on the store and only exports chat providers, which is inconsistent with the feature's goal. The importProviderConfigs function calls a method that doesn't exist, which will cause a runtime error. Suggestions have been provided to fix these bugs and improve the feature's correctness and completeness.

gemini-code-assist · 2026-03-22T09:42:25Z

+    Object.entries(config).forEach(([providerId, providerConfig]) => {
+      store.setProviderConfig(providerId, providerConfig)
+    })


The method store.setProviderConfig does not exist on the providers store. This will cause a runtime error. You should directly modify the providers state. Since store.providers is a ref, you need to assign to its .value property. A safe and efficient way to do this is to merge the imported configurations with the existing ones.

Suggested change

Object.entries(config).forEach(([providerId, providerConfig]) => {

store.setProviderConfig(providerId, providerConfig)

})

store.providers.value = {

...store.providers.value,

...config,

};

gemini-code-assist · 2026-03-22T09:42:25Z

+  const providerIds = store.configuredChatProviders.map(p => p.id)
+  providerIds.forEach(id => {
+    config[id] = store.getProviderConfig(id) || {}
+  })


The property store.configuredChatProviders does not exist. It seems you intended to use store.configuredChatProvidersMetadata. Additionally, this function only exports chat provider configurations, while the function name and PR description imply all provider configurations should be exported. To fix this and make it more robust, you could iterate over store.availableProviders which contains all configured providers regardless of their category.

Suggested change

const providerIds = store.configuredChatProviders.map(p => p.id)

providerIds.forEach(id => {

config[id] = store.getProviderConfig(id) || {}

})

for (const providerId of store.availableProviders) {

const providerConfig = store.getProviderConfig(providerId);

if (providerConfig) {

config[providerId] = providerConfig;

}

}

feat: add export/import for provider configurations

6cf8085

chatgpt-codex-connector Bot reviewed Mar 22, 2026

View reviewed changes

gemini-code-assist Bot reviewed Mar 22, 2026

View reviewed changes

nekomeowww added scope/providers Scope related to providers we support scope/ui Scope related to UI/UX, or interface improve, perf, and bugs labels Mar 26, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: add export/import for provider configurations#1450

feat: add export/import for provider configurations#1450
yudanmao123 wants to merge 1 commit intomoeru-ai:mainfrom
yudanmao123:main

yudanmao123 commented Mar 22, 2026

Uh oh!

gemini-code-assist Bot commented Mar 22, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Mar 22, 2026

Uh oh!

chatgpt-codex-connector Bot Mar 22, 2026

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

gemini-code-assist Bot Mar 22, 2026

Uh oh!

gemini-code-assist Bot Mar 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		Object.entries(config).forEach(([providerId, providerConfig]) => {
		store.setProviderConfig(providerId, providerConfig)

-    Object.entries(config).forEach(([providerId, providerConfig]) => {
-      store.setProviderConfig(providerId, providerConfig)
-    })
+    store.providers.value = {
+      ...store.providers.value,
+      ...config,
+    };

-  const providerIds = store.configuredChatProviders.map(p => p.id)
-  providerIds.forEach(id => {
-    config[id] = store.getProviderConfig(id) || {}
-  })
+  for (const providerId of store.availableProviders) {
+    const providerConfig = store.getProviderConfig(providerId);
+    if (providerConfig) {
+      config[providerId] = providerConfig;
+    }
+  }

Uh oh!

Conversation

yudanmao123 commented Mar 22, 2026

Uh oh!

gemini-code-assist Bot commented Mar 22, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Mar 22, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Mar 22, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist Bot Mar 22, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot Mar 22, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants