CherryHQ/cherry-studio

[Discussion]: Custom parameters are not correctly passed to the request body

Open

#14932 opened on May 8, 2026

View on GitHub
 (0 comments) (2 reactions) (0 assignees)TypeScript (45,688 stars) (4,338 forks)batch import
Assistantdiscussionhelp 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

Custom parameters are not correctly passed to the request body

Context

Custom Parameters were added in the 'Default Assistant' settings, but when actually sending the request, these parameters were not included in the final request body. This causes the API call to ignore these critical configurations (such as response_format and aspect_ratio)

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

自定义参数未正确传递至请求体

Context

在默认助手设置中添加了自定义参数（Custom Parameters），但在实际发送请求时，这些参数并没有被包含在最终的请求体中。这导致 API 调用忽略了这些关键配置（例如 response_format 和 aspect_ratio）

Additional Information

Priority

Medium (Would like a response soon)

Contributor guide

Tech stack
typescriptnodejsrest api
Domain
backendapi
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.
mostly clear
Prerequisites
basic TypeScriptunderstanding of HTTP requests
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate how custom parameters from 'Default Assistant' settings are stored and retrieved (likely in a config or store). Then trace the request building logic in the backend (e.g., in src/api or src/request) to find where the request body is assembled and ensure custom parameters are included. Look for any missing merge or spread operator in the object construction.