feat(dashboard): free-tier grouping with symbolic link in /providers

[diegosouzapw]

Summary

Implements task _tasks/features-v3.8.3/refactorpages/03-providers-free-tier-grouping.plan.md (Phase 1 of the v3.8.3 refactor).

The "Free" chip now works as a symbolic-link aggregation: every provider with hasFree: true shows up in the Free section and still appears in its native category — instead of disappearing when another category is active. Free providers gain a second amber dot next to the category color so they're visually identifiable even from inside their native list.

Key changes

• CategoryDot component — renders the category dot plus an optional free dot with localized tooltips (hasFreeTooltip).
• ProviderCard — uses CategoryDot so every card surfaces the free indicator next to the provider name.
• providers/page.tsx — replaces the old hardcoded FREE_SECTION_IDS set (27 IDs) with a dynamic entries.filter(hasFree). Text search dedupes by providerId so each provider appears only once even when it spans multiple categories; the Free section is hidden when search is active without an explicit category to avoid visual duplication. summaryStats.free is the aggregate count (overlap is intentional).
• 14 providers gained hasFree: true (80 → 94):
  • From 9router cross-check (plan §3.1): qoder, gemini-cli, kiro, amazon-q, opencode, ollama-cloud, vertex
  • Found in audit: tavily-search, exa-search, serper-search, brave-search, searxng-search (search providers with free tiers) and sdwebui, comfyui (local image providers — free by nature)
• i18n — added hasFreeTooltip and freeAggregated in en.json and pt-BR.json.

Files

New:

• src/app/(dashboard)/dashboard/providers/components/CategoryDot.tsx
• tests/unit/providers-free-tier-filter.test.ts

Modified:

• src/app/(dashboard)/dashboard/providers/components/ProviderCard.tsx
• src/app/(dashboard)/dashboard/providers/page.tsx
• src/shared/constants/providers.ts
• src/i18n/messages/en.json, src/i18n/messages/pt-BR.json

Validations

• npm run typecheck:core → clean
• npm run lint → 0 errors (pre-existing warnings only)
• node --import tsx/esm --test tests/unit/providers-free-tier-filter.test.ts → 5/5 pass

Test plan

• Open /dashboard/providers
• Click the "Free" chip — count is the aggregate (≥87 now), shows providers from all native categories
• Verify OpenRouter appears in both "API Key" and "Free"
• Verify a provider with hasFree shows two dots (category color + amber) next to its name
• Verify the "Free" chip itself shows two dots
• Search "open" — each matching provider appears exactly once, no duplication
• Toggle between categories — no regression, totals add up (sum of categories > "All" is intentional, Free is aggregate)
• Hover the second dot — tooltip "Free tier available" / "Tier gratuito disponível"

[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.

[gemini-code-assist]

Code Review

This pull request refactors the provider dashboard to dynamically identify and display free-tier providers using a new hasFree property in the provider metadata, replacing a hardcoded list. It introduces a reusable CategoryDot component for consistent status visualization and includes a new unit test suite for the filtering logic. Feedback focuses on performance optimizations in ProvidersPage.tsx, specifically recommending the use of useMemo to prevent redundant calculations and deduping of provider lists during component re-renders.

[gemini-code-assist]

The provider lists are being deduped twice and recalculated on every render. Since ProvidersPage re-renders on every search query change, this can be optimized by combining the lists and using useMemo. Additionally, the first dedupeProviderEntries call is redundant as the second one on the combined list will handle all duplicates.

  const dashboardProviderEntriesAll = useMemo(() => dedupeProviderEntries([
    ...oauthProviderEntriesAll,
    ...apiKeyProviderEntriesAll,
    ...webCookieProviderEntriesAll,
    ...localProviderEntriesAll,
    ...searchProviderEntriesAll,
    ...audioProviderEntriesAll,
    ...cloudAgentProviderEntriesAll,
    ...upstreamProxyEntriesAll,
    ...compatibleProviderEntriesAll,
  ] as DashboardProviderEntry[]), [
    oauthProviderEntriesAll,
    apiKeyProviderEntriesAll,
    webCookieProviderEntriesAll,
    localProviderEntriesAll,
    searchProviderEntriesAll,
    audioProviderEntriesAll,
    cloudAgentProviderEntriesAll,
    upstreamProxyEntriesAll,
    compatibleProviderEntriesAll,
  ]);

[gemini-code-assist]

These filtered lists should be memoized to avoid unnecessary array operations on every render, especially during search interactions when the component re-renders frequently.

Suggested change

	const freeSectionEntriesAll = dashboardProviderEntriesAll.filter(providerEntryHasFree);
	const freeSectionEntries = filterConfiguredProviderEntries(
	freeSectionEntriesAll,
	effectiveShowConfiguredOnly,
	const freeSectionEntriesAll = useMemo(() => dashboardProviderEntriesAll.filter(providerEntryHasFree), [dashboardProviderEntriesAll]);
	const freeSectionEntries = useMemo(() => filterConfiguredProviderEntries(
	freeSectionEntriesAll,
	effectiveShowConfiguredOnly,
	showFreeOnly
	), [freeSectionEntriesAll, effectiveShowConfiguredOnly, showFreeOnly]);

[gemini-code-assist]

The summaryStats object is recalculated on every render. Memoizing it will prevent unnecessary filtering and counting operations when the underlying provider lists haven't changed.

  const summaryStats = useMemo(() => ({
    all: countConfigured(dashboardProviderEntriesAll),
    free: countConfigured(freeSectionEntriesAll),
    oauth: countConfigured(oauthOnlyEntriesAll),
    apikey: countConfigured(apiKeyProviderEntriesAll),
  }), [dashboardProviderEntriesAll, freeSectionEntriesAll, oauthOnlyEntriesAll, apiKeyProviderEntriesAll]);

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7b861392b0

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align free batch testing with aggregated free section

The new freeSectionEntriesAll now pulls every hasFree provider from all categories, so the Free section can include Search/Local/API-key providers (e.g., tavily-search, comfyui, openrouter). However, the Free section still triggers handleBatchTest("free"), and the API route for mode free only tests providers whose auth group is literally "free" (from FREE_PROVIDERS). This means users clicking Test All in the Free section will silently skip many cards shown in that same section, producing incomplete/incorrect test results.

Useful? React with 👍 / 👎.

[github-actions]

CI Coverage Report

• Coverage job: failure
• PR test policy: success

Coverage artifact was not available for this run.