fix(playground): filter playground models by node prefix so custom-endpoint models appear (#3505)

[diegosouzapw]

Closes #3505

Problem: the dashboard playground (StudioConfigPane) filtered /v1/models by the provider OPTION VALUE — the connection id (openai-compatible-<uuid>) for compatible providers — but the catalog emits those models under the node's custom PREFIX (myprefix/gpt-4o), so the selector showed "None"/"-". (#3200 only fixed no-auth providers.)

Fix (safe, local): useProviderOptions exposes modelPrefix additively (the value stays the connection id — translator send/translate + ApiTab connection lookups unaffected); the playground filters by it. Extracted filterModelsByProvider() (pure) for testing.

Test (Rule #18): tests/unit/playground-model-filter-3505.test.ts (RED before the export). #3200 + models-catalog suites green; typecheck clean. End-to-end UI confirmation recommended at release smoke.

[gemini-code-assist]

Code Review

This pull request fixes an issue where the playground model selector failed to list models from custom-endpoint providers by filtering models using the provider's custom prefix instead of its connection ID. It exposes the modelPrefix in provider options, extracts the filtering logic into a pure filterModelsByProvider function, and adds a unit test suite. The review feedback recommends using optional chaining on providerOptions to prevent potential runtime errors during loading states, and migrating the unit tests from Node's native test runner to Vitest to align with the project's testing standards.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Use optional chaining (providerOptions?.find) to safely handle cases where providerOptions might be null or undefined (e.g., during initial load or error states). This aligns with defensive programming practices to prevent runtime TypeError crashes.

Suggested change

	const selectedProviderOption = providerOptions.find(
	(opt: { value: string; modelPrefix?: string }) => opt.value === provider
	);
	const selectedProviderOption = providerOptions?.find(
	(opt: { value: string; modelPrefix?: string }) => opt.value === provider
	);

[gemini-code-assist]

Since the project standardizes on Vitest (as indicated by vitest.config.ts), writing tests using Node's native node:test and node:assert introduces inconsistency. Migrating this test file to use Vitest's native describe, it, and expect APIs will improve consistency and integration with the test suite. Additionally, importing with a .tsx extension should be avoided to prevent potential TypeScript compilation or module resolution issues.

import { describe, it, expect } from "vitest";
import { filterModelsByProvider } from "../../src/app/(dashboard)/dashboard/translator/hooks/useAvailableModels";

// Regression for #3505: the playground model selector filtered the /v1/models list by the
// provider OPTION VALUE (a compatible provider's node id, e.g. "openai-compatible-<uuid>"),
// but the catalog emits compatible-provider models under the node's custom PREFIX
// (e.g. "myprefix/gpt-4o"). So `startsWith("openai-compatible-<uuid>/")` matched nothing and
// the selector showed "None"/"-". The fix passes the node prefix as the filter key. This locks
// the filter behaviour: given the right key (the prefix), the models surface.

describe("#3505 playground model filter", () => {
  it("filters models by a custom node prefix (the catalog's model namespace)", () => {
    const all = ["myprefix/gpt-4o", "myprefix/llama-3", "openai/gpt-4o", "anthropic/claude-opus-4-8"];
    expect(filterModelsByProvider(all, "myprefix")).toEqual(["myprefix/gpt-4o", "myprefix/llama-3"]);
  });

  it("a UUID-style node id (the old wrong key) matches nothing → empty (the bug)", () => {
    const all = ["myprefix/gpt-4o", "openai/gpt-4o"];
    expect(filterModelsByProvider(all, "openai-compatible-1234-uuid")).toEqual([]);
  });

  it("built-in provider filtering still works", () => {
    const all = ["openai/gpt-4o", "openai/gpt-4o-mini", "anthropic/claude-opus-4-8"];
    expect(filterModelsByProvider(all, "openai")).toEqual(["openai/gpt-4o", "openai/gpt-4o-mini"]);
  });

  it("an exact bare match is included; no provider returns all", () => {
    expect(filterModelsByProvider(["auto", "openai/gpt-4o"], "auto")).toEqual(["auto"]);
    expect(filterModelsByProvider(["a", "b"], undefined)).toEqual(["a", "b"]);
  });
});

[kilo-code-bot]

Kilo Code Review could not run — your account is out of credits.

Add credits or switch to a free model to enable reviews on this change.

[tjengbudi]

@diegosouzapw
i using 3.8.20 docker

and it still not working