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.

Closed

#14,334 opened on Apr 17, 2026

View on GitHubContributor guide
 (1 comment) (1 reaction) (0 assignees)TypeScript (4,338 forks)batch import
Modelsdiscussionhelp wantedinactive

Repository metrics

Stars
 (45,688 stars)
PR merge metrics
 (Avg merge 3d 6h) (306 merged PRs in 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)

Contributor guide

Research direction
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
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Familiarity with Cherry Studio's supplier configurationBasic React and state management knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65