Northern_Lights/cherry-studio
1
0
Fork 0
mirror of https://github.com/CherryHQ/cherry-studio.git synced 2026-01-08 14:29:15 +08:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

fix: Grouped message should not reset model and modelId

Browse Source 
* Updated the reset logic to conditionally handle model and modelId for grouped messages.
* Ensured that the original model is retained when regenerating responses for grouped messages.
This commit is contained in:
kangfenmao 2025-05-13 20:41:15 +08:00
parent ff8224a2dc
commit 02ae0349bf
1 changed files with 14 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
src/renderer/src/store/thunk/messageThunk.ts
View File

@ -987,12 +987,20 @@ export const regenerateAssistantResponseThunk =
const blockIdsToDelete = [...(messageToResetEntity.blocks || [])] const blockIdsToDelete = [...(messageToResetEntity.blocks || [])]
// 5. Reset the message entity in Redux // 5. Reset the message entity in Redux
const resetAssistantMsg = resetAssistantMessage(messageToResetEntity, { const resetAssistantMsg = resetAssistantMessage(
status: AssistantMessageStatus.PENDING, messageToResetEntity,
updatedAt: new Date().toISOString(), // Grouped message (mentioned model message) should not reset model and modelId, always use the original model
model: assistant.model, assistantMessageToRegenerate.modelId
modelId: assistant?.model?.id ? {
}) status: AssistantMessageStatus.PENDING,
updatedAt: new Date().toISOString()
}
: {
status: AssistantMessageStatus.PENDING,
updatedAt: new Date().toISOString(),
model: assistant.model
}
)
dispatch( dispatch(
newMessagesActions.updateMessage({ newMessagesActions.updateMessage({