Skip to content

Commit 172df1d

Browse files
joybnuuyclaude
andcommitted
fix: always include reasoning_content on assistant messages for proxy compat
Moonshot's API rejects assistant messages without reasoning_content when thinking is enabled (which proxies like OpenCode Go enable server-side). Empty string is also rejected — use a single space as fallback. Fixes tool-call failures through OpenCode Go proxy (anomalyco/opencode#10996). Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
1 parent 3e2b11b commit 172df1d

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

  • packages/kosong/src/kosong/chat_provider

‎packages/kosong/src/kosong/chat_provider/kimi.py‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -297,8 +297,12 @@ def _convert_message(message: Message) -> ChatCompletionMessageParam:
297297
content.append(part)
298298
message.content = content
299299
dumped_message = message.model_dump(exclude_none=True)
300-
if reasoning_content:
301-
dumped_message["reasoning_content"] = reasoning_content
300+
# Always include reasoning_content on assistant messages. Moonshot's API
301+
# requires this field when thinking is enabled (which proxies like OpenCode
302+
# Go may enable server-side). Use a single space when no thinking output
303+
# exists — empty string may be rejected.
304+
if message.role == "assistant":
305+
dumped_message["reasoning_content"] = reasoning_content or " "
302306
return cast(ChatCompletionMessageParam, dumped_message)
303307

304308

0 commit comments

Comments
 (0)