[FEAT]: Disable Temperature Setting for DeepSeek-R1 (deepseek-reasoner) Model

[spencerthayer]

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.

[timothycarambat]

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

[shatfield4]

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

[spencerthayer]

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