Skip to content

Commit 0bd06bb

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 5ce86f9 commit 0bd06bb

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
@@ -296,8 +296,12 @@ def _convert_message(message: Message) -> ChatCompletionMessageParam:
296296
content.append(part)
297297
message.content = content
298298
dumped_message = message.model_dump(exclude_none=True)
299-
if reasoning_content:
300-
dumped_message["reasoning_content"] = reasoning_content
299+
# Always include reasoning_content on assistant messages. Moonshot's API
300+
# requires this field when thinking is enabled (which proxies like OpenCode
301+
# Go may enable server-side). Use a single space when no thinking output
302+
# exists — empty string may be rejected.
303+
if message.role == "assistant":
304+
dumped_message["reasoning_content"] = reasoning_content or " "
301305
return cast(ChatCompletionMessageParam, dumped_message)
302306

303307

0 commit comments

Comments
 (0)