You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Kimi K2.6] reasoning_content is missing in assistant tool call messages #29619
When using OpenCode with Kimi K2.6, tool calls fail with:
[Moonshot AI] thinking is enabled but reasoning_content is missing in assistant tool call message at index N
Environment
OpenCode: latest
Provider: Moonshot AI / Kimi K2.6
Model: kimi-k2.6
Thinking mode: enabled
Tool calls: enabled
Steps to reproduce
Use Kimi K2.6 with thinking enabled.
Ask the agent to perform a task that requires tool calls.
After the first assistant/tool-call roundtrip, the next request fails.
Expected behavior
OpenCode should preserve and resend reasoning_content in assistant messages that contain tool calls.
Actual behavior
Moonshot rejects the request because reasoning_content is missing from the assistant tool call message.
Notes
This appears to happen specifically with Kimi K2.6 and tool calling.
The issue seems related to reasoning-content preservation across the tool-call roundtrip.
I’ve seen at least five issues regarding the same problem, and there are quite a few pull requests as well. It’s strange that these PRs still haven’t been reviewed.
I understand that many PRs may not actually fix the issue.
But #25011 seems to target the Moonshot/Kimi message-format problem and was closed by automated cleanup without review.
So this still looks like a maintainer review/backlog problem, not only a PR quality problem.
Activity
github-actions commentedon May 27, 2026
This issue might be a duplicate of existing issues. Please check:
reasoning_contentin tool call message historyreasoning_contentnot passed back for tool call turns (same root cause pattern)If your issue is specific to a different scenario or version, please add details clarifying how it differs from the above.
rekram1-node commentedon May 27, 2026
can u send the session?
opencode export > session.json
do not run /export
MrCh1ppy commentedon Jun 2, 2026
I’ve seen at least five issues regarding the same problem, and there are quite a few pull requests as well. It’s strange that these PRs still haven’t been reviewed.
rekram1-node commentedon Jun 2, 2026
@MrCh1ppy thats because vast majority of PRs:
MrCh1ppy commentedon Jun 3, 2026
I understand that many PRs may not actually fix the issue.
But #25011 seems to target the Moonshot/Kimi message-format problem and was closed by automated cleanup without review.
So this still looks like a maintainer review/backlog problem, not only a PR quality problem.
rekram1-node commentedon Jun 3, 2026
That was my own PR haha and it's not a fix for this issue it's a separate one and I havent flushed it out yet
github-actions commentedon Aug 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.