feat(versioning): set initial version to 0.0.1 and restore dynamic model import

[diegosouzapw]

• Set package.json and open-sse/package.json to v0.0.1
• Restore 'Import from /models' button for all standard providers
• Add handleImportModels to ProviderDetailPage

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[gemini-code-assist]

Summary of Changes

Hello @diegosouzapw, 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 establishes an initial versioning baseline for the project's packages and reintroduces a crucial feature for managing provider models. It enables users to dynamically import available models directly from their configured providers, enhancing the flexibility and ease of setup for new integrations. The changes ensure that the application's versioning is properly initialized and that model management is more streamlined.

Highlights

• Versioning: The package.json files for both the main application and the open-sse package have been updated to an initial version of 0.0.1.
• Model Import Functionality: The 'Import from /models' button has been restored and integrated into the ProviderDetailPage, allowing users to dynamically import models for standard providers.
• New Model Import Handler: A new asynchronous function, handleImportModels, has been added to manage the process of fetching and importing models from a provider's /models endpoint, including error handling and alias creation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• open-sse/package.json
  • Updated the package version from 1.0.0 to 0.0.1.
• package.json
  • Updated the application version from 0.2.73 to 0.0.1.
• src/app/(dashboard)/dashboard/providers/[id]/page.js
  • Added a new state variable importingModels to manage the UI state during model import.
  • Implemented the handleImportModels asynchronous function to fetch models from the provider API, handle responses, and create aliases for new models.
  • Introduced a canImportModels derived state to control the availability of the import button.
  • Integrated the 'Import from /models' button into the renderModelsSection for both cases where models are present or absent, providing visual feedback during the import process and guidance when no connections are active.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. 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. ↩

[github-actions]

@codex review

[chatgpt-codex-connector]

To use Codex here, create a Codex account and connect to github.

[Copilot]

Pull request overview

This PR resets the monorepo package versions to an initial 0.0.1 and restores the ability to import provider models from the /models endpoint on the Provider detail page for non-compatible (“standard”) providers.

Changes:

• Set root package.json version to 0.0.1.
• Set open-sse/package.json version to 0.0.1.
• Add handleImportModels + UI button to import models from /api/providers/:id/models for standard providers.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
src/app/(dashboard)/dashboard/providers/[id]/page.js	Adds state + handler + UI button to import models from /models for standard providers.
package.json	Resets app version to 0.0.1 (used by APP_CONFIG.version).
open-sse/package.json	Resets workspace package version to 0.0.1.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

handleImportModels skips any model whose base alias already exists (if (modelAliases[baseAlias]) continue;). Since aliases are global, this can prevent importing models for this provider whenever another provider already uses the same base alias. Consider using the same alias resolution strategy as CompatibleModelsSection (e.g., fall back to a provider-prefixed alias) and track aliases added during this import so duplicates within the same /models response don’t attempt to reuse the same alias.

Suggested change

	let importedCount = 0;
	for (const model of fetchedModels) {
	const modelId = model.id || model.name || model.model;
	if (!modelId) continue;
	const parts = modelId.split("/");
	const baseAlias = parts[parts.length - 1];
	if (modelAliases[baseAlias]) continue;
	await handleSetAlias(modelId, baseAlias, providerStorageAlias);
	// Track aliases already in use globally and those added during this import
	const usedAliases = new Set(
	modelAliases ? Object.keys(modelAliases) : []
	);
	let importedCount = 0;
	for (const model of fetchedModels) {
	const modelId = model.id || model.name || model.model;
	if (!modelId) continue;
	const parts = modelId.split("/");
	const baseAlias = parts[parts.length - 1];
	// Resolve a unique alias, falling back to provider-prefixed names if needed
	let aliasToUse = baseAlias;
	if (usedAliases.has(aliasToUse)) {
	const providerPrefixedBase = `${providerStorageAlias}-${baseAlias}`;
	aliasToUse = providerPrefixedBase;
	let counter = 2;
	while (usedAliases.has(aliasToUse)) {
	aliasToUse = `${providerPrefixedBase}-${counter}`;
	counter += 1;
	}
	}
	await handleSetAlias(modelId, aliasToUse, providerStorageAlias);
	usedAliases.add(aliasToUse);

[Copilot]

Importing models currently results in many redundant alias refreshes: handleSetAlias calls fetchAliases() on every successful PUT, and handleImportModels also calls fetchAliases() again at the end. For providers returning large /models lists this will be noticeably slow. Consider deferring alias refresh during bulk import (e.g., add a flag to handleSetAlias to skip fetchAliases, then refresh once after the loop).

Suggested change

await fetchAliases();

[Copilot]

const data = await res.json(); will throw if the /api/providers/${id}/models endpoint returns a non-JSON error (e.g., HTML from a proxy), and the catch block only logs to console (no user feedback). Align with the pattern used elsewhere in this file (e.g., res.json().catch(() => ({}))) and surface an error to the user when parsing fails.

[Copilot]

When getModelsByProviderId(providerId) returns an empty list, the UI will continue to show “No models configured” even after a successful import, because the section renders from the static models list rather than the imported aliases. Consider rendering imported models (e.g., based on modelAliases filtered by providerStorageAlias) or at least showing a success count so users can confirm the import worked.

[gemini-code-assist]

Code Review

This pull request sets initial package versions and restores dynamic model import functionality for standard providers. However, a medium-severity Stored XSS vulnerability was identified in the new handleImportModels function, where the model ID from external providers is not sanitized before storage, potentially allowing malicious payloads. It is recommended to validate the model ID against a strict format. Additionally, there are suggestions to improve error handling, make the model import logic more robust, and refactor the rendering logic for better maintainability.

[gemini-code-assist]

The user is not notified if an unexpected error occurs during model import (e.g., a network issue). The error is only logged to the console, which is not visible to the end-user. It's better to display an alert to inform the user about the failure, consistent with how other errors are handled in this function. Also, it's a good practice to use console.error for logging errors.

Suggested change

	console.log("Error importing models:", error);
	console.error("Error importing models:", error);
	alert(`An error occurred while importing models: ${error.message}`);

[gemini-code-assist]

The handleImportModels function fetches model.id from external providers, which is then used to generate a baseAlias and stored in the database. This modelId is not validated or sanitized, posing a Stored XSS risk if a malicious or compromised provider returns a harmful payload. It is critical to validate the modelId against a strict format (e.g., alphanumeric characters, dashes, dots, and slashes) before processing it, as the application should not implicitly trust data from third-party APIs.

Additionally, the current implementation silently skips models if their baseAlias already exists, which can be confusing for users. A more robust approach would be to attempt to create a prefixed alias if the base alias is taken, similar to the resolveAlias logic in CompatibleModelsSection, to increase the chance of successfully importing all models.

[gemini-code-assist]

The rendering logic for the models section can be simplified to avoid repeating the wrapper div and the importButton. You can use a conditional (ternary) operator to render either the 'No models' message or the list of models within a single structure.

    return (
      <div>
        {importButton}
        {models.length === 0 ? (
          <p className="text-sm text-text-muted">No models configured</p>
        ) : (
          <div className="flex flex-wrap gap-3">
            {models.map((model) => {
              const fullModel = `${providerStorageAlias}/${model.id}`;
              const oldFormatModel = `${providerId}/${model.id}`;
              const existingAlias = Object.entries(modelAliases).find(
                ([, m]) => m === fullModel || m === oldFormatModel,
              )?.[0];
              return (
                <ModelRow
                  key={model.id}
                  model={model}
                  fullModel={`${providerDisplayAlias}/${model.id}`}
                  alias={existingAlias}
                  copied={copied}
                  onCopy={copy}
                  onSetAlias={(alias) => handleSetAlias(model.id, alias, providerStorageAlias)}
                  onDeleteAlias={() => handleDeleteAlias(existingAlias)}
                />
              );
            })}
          </div>
        )}
      </div>
    );