From c2a5c7a24e1e132acf37a457f05fceb2c54dee5e Mon Sep 17 00:00:00 2001
From: Classic298 <27028174+Classic298@users.noreply.github.com>
Date: Sat, 10 Oct 2026 18:12:45 +0200
Subject: [PATCH] fix: switching a Chat Controls parameter back to Default
 ignores your Settings value (#32192)

When a parameter like Temperature was switched to Custom in Chat Controls and then back to Default, the value saved in Settings > General was dropped and the model used its built-in default instead. Default now uses the Settings value again, also in chats where this already happened.

Fixes #32013
---
 src/lib/components/chat/Chat.svelte | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/lib/components/chat/Chat.svelte b/src/lib/components/chat/Chat.svelte
index a93913cf18..9e01ef6df3 100644
--- a/src/lib/components/chat/Chat.svelte
+++ b/src/lib/components/chat/Chat.svelte
@@ -4039,7 +4039,7 @@
 				...(messages.length > 0 ? { messages } : {}),
 				params: {
 					...$settings?.params,
-					...params,
+					...Object.fromEntries(Object.entries(params).filter(([, value]) => value !== null)),
 					model_controls: $settings?.params?.model_controls ?? {},
 					stop: getStopTokens()
 				},