CherryHQ/cherry-studio

[Discussion]: How to configure a non-standard API path without v1 prefix

Open

#14933 opened on May 8, 2026

View on GitHub
 (0 comments) (1 reaction) (0 assignees)TypeScript (45,688 stars) (4,338 forks)batch import
discussionhelp wanted

Description

[!NOTE] This issue was translated by Claude.

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

Your Question

I have a non-standard API path with the URL httpps://x.x.x/chat/completions. There is no v1 prefix. How should I configure this?

Context

No response

Additional Information

Priority

Medium (Would like a response soon)

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

Your Question

我现在有一个非标准路径的api，路径为httpps://x.x.x/chat/completions。没有v1，我应该如何设置

Context

No response

Additional Information

Priority

Medium (Would like a response soon)

Contributor guide

Tech stack
typescriptnodejsrest api
Domain
backendapi
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
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.
mostly clear
Prerequisites
Basic API configuration knowledgeFamiliarity with Cherry Studio settings
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The user wants to configure a non standard API path without the v1 prefix (e.g., https://x.x.x/chat/completions). No additional context or configuration details are provided. The resolution likely involves checking the repository's documentation or default configuration files (e.g., src/config, .env, or API provider setup) for a custom path option. Maintainers may need to clarify where such a setting exists or suggest a workaround.