fix(provider): enable reasoning_split for MiniMax to separate CoT from content
MiniMax's v1/chat/completions endpoint includes chain-of-thought in the content field by default, causing thinking content to leak into user-visible responses. This fix enables reasoning_split parameter for MiniMax API requests to separate CoT into reasoning_details field. Fixes #1320
This commit is contained in:
parent
e74820cf69
commit
ede7cc7045
1 changed files with 7 additions and 0 deletions
|
|
@ -163,6 +163,13 @@ func (p *Provider) Chat(
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
// MiniMax provider: enable reasoning_split to separate CoT from content
|
||||||
|
// This prevents chain-of-thought from leaking into the main content field.
|
||||||
|
// See: https://github.com/sipeed/picoclaw/issues/1320
|
||||||
|
if strings.Contains(strings.ToLower(p.apiBase), "minimaxi.com") {
|
||||||
|
requestBody["reasoning_split"] = true
|
||||||
|
}
|
||||||
|
|
||||||
jsonData, err := json.Marshal(requestBody)
|
jsonData, err := json.Marshal(requestBody)
|
||||||
if err != nil {
|
if err != nil {
|
||||||
return nil, fmt.Errorf("failed to marshal request: %w", err)
|
return nil, fmt.Errorf("failed to marshal request: %w", err)
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue