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.

Fermée

#14 334 ouverte le 17 avr. 2026

Voir sur GitHubGuide contributeur
 (1 commentaire) (1 réaction) (0 personne assignée)TypeScript (4 338 forks)batch import
Modelsdiscussionhelp wantedinactive

Métriques du dépôt

Stars
 (45 688 étoiles)
Métriques de merge PR
 (Merge moyen 3j 6h) (306 PRs mergées en 30 j)

Description

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)

Guide contributeur

Direction de recherche
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.
Stack technique
typescriptreactnodejsrest api
Domaine
full stackfrontendbackend
Type d'issue
Bug
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 heures
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
Récente
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
Claire
Prérequis
Familiarity with Cherry Studio's supplier configurationBasic React and state management knowledge
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
65