CherryHQ/cherry-studio

[Discussion]: After configuring a custom supplier, the API can successfully request the model list data, but the model selection bar within the software displays as empty/without any models.

Geschlossen

#14.334 geöffnet am 17.04.2026

Auf GitHub ansehenContributor Guide
 (1 Kommentar) (1 Reaktion) (0 zugewiesene Personen)TypeScript (4.338 Forks)batch import
Modelsdiscussionhelp wantedinactive

Repository-Metriken

Stars
 (45.688 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 3T 6h) (306 gemergte PRs in 30 T)

Beschreibung

Issue Checklist

  • I understand that issues are meant for feedback and problem-solving, not for venting, and I will provide as much detail as possible to help resolve the issue.
  • I have checked the pinned issues and searched through the existing open issues, closed issues, and discussions and did not find a similar suggestion.
  • I confirm that I am here to ask questions and discuss issues, not to report bugs or request features.

Platform

Windows

Version

v1.9.1

Your Question

Problem Description: After configuring a custom supplier, the API can successfully request the model list data, but the model selection bar within the software is empty/shows no models.

Context

Additional Information

Priority

Medium (Would like a response soon)

Contributor Guide

Research-Richtung
Investigate the component that renders the model selection bar. Check the data flow from the API response to the UI state. Look for how the model list is stored and filtered. Possibly the response format differs from what the UI expects. Examine the supplier configuration and model parsing logic. Consider if the `id` or `name` fields are missing or mismatched.
Tech Stack
typescriptreactnodejsrest api
Domain
full stackfrontendbackend
Issue Type
Fehler
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
1-3 Stunden
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
Frisch
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
Klar
Voraussetzungen
Familiarity with Cherry Studio's supplier configurationBasic React and state management knowledge
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
65