CherryHQ/cherry-studio

[Discussion]: Deepseek-v4-flash api close thinking model

Closed

#15,199 opened on May 20, 2026

View on GitHubContributor guide
 (0 comments) (2 reactions) (0 assignees)TypeScript (4,338 forks)batch import
Modelsdiscussionhelp wanted

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

1.9.6

Your Question

When I call the deepseek-v4-flash API in Cherry Studio, I use some agents for translation and paper reading. However, the model enters thinking mode every time. For these use cases, I do not need thinking mode. How can I disable it? I have tried turning off “Thinking” in the Advanced Settings of the Cherry Studio interface, but it does not seem to take effect. So I would like to report this issue and hope it can be fixed in the next version update. Thank you.

Context

No response

Additional Information

Priority

Medium (Would like a response soon)

Contributor guide

Research direction
Investigate why the 'Thinking' toggle in advanced settings does not disable thinking mode for Deepseek v4 flash API calls. Check the state management of model settings and the API request builder to see if the thinking parameter is correctly passed.
Tech stack
typescript
Domain
frontend
Issue type
Bug
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70