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.

Fechada

#14.334 aberto em 17 de abr. de 2026

Ver no GitHubGuia do colaborador
 (1 comentário) (1 reação) (0 responsável)TypeScript (4.338 forks)batch import
Modelsdiscussionhelp wantedinactive

Métricas do repositório

Stars
 (45.688 estrelas)
Métricas de merge de PR
 (Mesclagem média 3d 6h) (306 fundiu PRs em 30d)

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)

Guia do colaborador

Direção de pesquisa
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.
Pilha de tecnologia
typescriptreactnodejsrest api
Domain
full stackfrontendbackend
Tipo Issue
Bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 horas
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
Recente
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
Claro
Prerequisites
Familiarity with Cherry Studio's supplier configurationBasic React and state management knowledge
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
65