Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2995] [FEAT]: Disable Temperature Setting for DeepSeek-R1 (deepseek-reasoner) Model #1917

New Issue
Closed
opened 2026-02-22 18:27:13 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:27:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @spencerthayer on GitHub (Jan 20, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2995

Originally assigned to: @shatfield4 on GitHub.

When using the DeepSeek-R1 model (identified as deepseek-reasoner in AnythingLLM), the following error occurs, preventing successful message processing:

Could not respond to message.

400 deepseek-reasoner does not support the parameter `temperature`

This error arises because the DeepSeek-R1 model, as documented in the official DeepSeek-R1 repository (https://github.com/deepseek-ai/DeepSeek-R1#1-introduction), is specifically trained using Reinforcement Learning (RL) and does not support the temperature parameter. Attempting to include this parameter in API requests to the model results in the reported 400 error.

Currently, AnythingLLM presents the temperature setting as a configurable option in the UI for all language models, including deepseek-reasoner. This feature request aims to resolve this incompatibility and improve the user experience by disabling or hiding the temperature setting when the deepseek-reasoner model is selected.

Originally created by @spencerthayer on GitHub (Jan 20, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2995 Originally assigned to: @shatfield4 on GitHub. When using the DeepSeek-R1 model (identified as `deepseek-reasoner` in AnythingLLM), the following error occurs, preventing successful message processing: ``` Could not respond to message. 400 deepseek-reasoner does not support the parameter `temperature` ``` This error arises because the DeepSeek-R1 model, as documented in the official DeepSeek-R1 repository ([https://github.com/deepseek-ai/DeepSeek-R1#1-introduction](https://github.com/deepseek-ai/DeepSeek-R1#1-introduction)), is specifically trained using Reinforcement Learning (RL) and does not support the `temperature` parameter. Attempting to include this parameter in API requests to the model results in the reported `400` error. Currently, AnythingLLM presents the temperature setting as a configurable option in the UI for all language models, including `deepseek-reasoner`. This feature request aims to resolve this incompatibility and improve the user experience by disabling or hiding the temperature setting when the `deepseek-reasoner` model is selected.
yindo added the bugIntegration Request labels 2026-02-22 18:27:13 -05:00
yindo closed this issue 2026-02-22 18:27:13 -05:00
yindo commented 2026-02-22 18:27:13 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 20, 2025):

@spencerthayer I don't know if you generate these issues programmatically or with AI, but please don't. We review every issue and having to parse though 99% noise and suggested changes that reference files that do not even exist, are in a format that does not apply to the codebase, or otherwise really amounts to us just spending more time looking at and triaging an issue that we should.

Next time, just use the bug template and any relevant information for replication. Anyone who picks up the issue would easily be able to to repro and identify the root cause from just that information. No need to propose changes unless it comes with an associated PR.

@timothycarambat commented on GitHub (Jan 20, 2025): @spencerthayer I don't know if you generate these issues programmatically or with AI, but please don't. We review every issue and having to parse though 99% noise and suggested changes that reference files that do not even exist, are in a format that does not apply to the codebase, or otherwise really amounts to us just spending more time looking at and triaging an issue that we should. Next time, just use the bug template and any relevant information for replication. Anyone who picks up the issue would easily be able to to repro and identify the root cause from just that information. No need to propose changes unless it comes with an associated PR.
yindo commented 2026-02-22 18:27:13 -05:00
Author
Owner
Copy Link
Copy Source

@shatfield4 commented on GitHub (Jan 21, 2025):

@spencerthayer is this still an issue for you? Are you running this locally or through their API?

I am trying to repro and I am unable to get that error with the deepseek-reasoner model via their API. I've tried modifying the default temperature as well and it responds normally for me.

@shatfield4 commented on GitHub (Jan 21, 2025): @spencerthayer is this still an issue for you? Are you running this locally or through their API? I am trying to repro and I am unable to get that error with the `deepseek-reasoner` model via their API. I've tried modifying the default temperature as well and it responds normally for me.
yindo commented 2026-02-22 18:27:13 -05:00
Author
Owner
Copy Link
Copy Source

@spencerthayer commented on GitHub (Jan 21, 2025):

No problem. I've booted up a dev fork.

@spencerthayer commented on GitHub (Jan 21, 2025): No problem. I've booted up a dev fork.
yindo changed title from [FEAT]: Disable Temperature Setting for DeepSeek-R1 (`deepseek-reasoner`) Model to [GH-ISSUE #2995] [FEAT]: Disable Temperature Setting for DeepSeek-R1 (`deepseek-reasoner`) Model 2026-06-05 14:43:27 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label Integration Request bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1917
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?