Kilo Kimi K2.6 requests send invalid reasoning_details

[joshbochu]

Kilo Gateway requests for moonshotai/kimi-k2.6 can fail with a 500 after a prior assistant reasoning turn.

The request body includes reasoning_details as a plain string derived from reasoning text. Kilo/OpenRouter-style reasoning_details should be structured data, so opencode should not synthesize that field from plain reasoning text.

Repro context:

• provider: kilo
• model: moonshotai/kimi-k2.6
• base URL: https://api.kilo.ai/api/gateway
• failing request includes assistant reasoning plus tool calls and sends reasoning_details: "..."

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• No issue template was used. Please resubmit using one of the required templates: Bug Report, Feature Request, or Question. The bug report template requires fields like Description, Steps to Reproduce, OpenCode version, and Operating System.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• Using reasoning models with OpenRouter provider yields "provider error" due rewritten reasoning blocks. #14716: Reasoning blocks being rewritten/replayed incorrectly for OpenRouter-style providers causes provider errors — similar root cause involving reasoning_details/reasoning_content being improperly synthesized or rewritten during message replay.
• Bedrock Claude Opus 4.7 replays thinking blocks through interleaved OpenAI-compatible transform #23926: Interleaved OpenAI-compatible reasoning transform applied incorrectly, stripping native reasoning structure and causing request failures on replay.
• reasoning_content stripped from assistant messages on replay, causing KV cache invalidation on local inference #19081: reasoning_content stripped from assistant messages on replay, causing failures with strict providers.

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.

[rekram1-node]

tbh idk how it's supposed to work can u provide more details and a session, i dont use kilo

[joshbochu]

np - im closing since it looks to have gone away on update