🐞 fix(settings): Fix Wrong model after login (#213)

Previously we were spreading the entire `prevCachedState.apiConfiguration` object when the keys changed, which would wipe out unsaved changes the user might have made to things like `prevCachedState.apiConfiguration.kiloModel`. Now we only set the keys that might be set via callback and don't trigger a save explicitly. The user will need to click 'save' in order to exit the SettingView like normal (same as changing any other setting).

- update state with specific tokens/keys to avoid overwriting unsaved changes
- simplify useEffect dependencies by using direct variables

**Dev thoughts**
This does make me think.. should "login" keys / tokens be a "setting"? seems like it should be in the Settings view UI, but possibly separate from the other settings state of the api. I feel like it's not intuitive to have to click a "save" button once you login to something for it to remain saved.

**Test plan**: Verified that logging in / out no longer overwrites other non-saved changes in the Settings. Now users will have to click save for any changes they make, including login state. (This should be ok since we have that confirmation dialog if they don't.)

**Closes** #123

Author: hassoncs

.changeset/sharp-colts-add.md

@@ -0,0 +1,5 @@
+---
+"kilo-code": patch
+---
+
+Fix wrong model after login (#213)

webview-ui/src/components/settings/SettingsView.tsx

@@ -172,16 +172,22 @@ const SettingsView = forwardRef<SettingsViewRef, SettingsViewProps>(({ onDone, o
 	// kilocode_change start
 	// Temporary way of making sure that the Settings view updates its local state properly when receiving
 	// api keys from providers that support url callbacks. This whole Settings View needs proper with this local state thing later
+	const { kilocodeToken, openRouterApiKey, glamaApiKey, requestyApiKey } = extensionState.apiConfiguration ?? {}
 	useEffect(() => {
-		setCachedState((prevCachedState) => ({ ...prevCachedState, ...extensionState }))
-		setChangeDetected(false)
+		setCachedState((prevCachedState) => ({
+			...prevCachedState,
+			apiConfiguration: {
+				...prevCachedState.apiConfiguration,
+				// Only set specific tokens/keys instead of spreading the entire
+				// `prevCachedState.apiConfiguration` since it may contain unsaved changes
+				kilocodeToken,
+				openRouterApiKey,
+				glamaApiKey,
+				requestyApiKey,
+			},
+		}))
 		// eslint-disable-next-line react-hooks/exhaustive-deps
-	}, [
-		extensionState.apiConfiguration?.kilocodeToken,
-		extensionState.apiConfiguration?.openRouterApiKey,
-		extensionState.apiConfiguration?.glamaApiKey,
-		extensionState.apiConfiguration?.requestyApiKey,
-	])
+	}, [kilocodeToken, openRouterApiKey, glamaApiKey, requestyApiKey])
 
 	useEffect(() => {
 		// Only update if we're not already detecting changes