fix(opencode): avoid invalid Kilo reasoning details#24411
Open
joshbochu wants to merge 1 commit intoanomalyco:devfrom
Open
fix(opencode): avoid invalid Kilo reasoning details#24411joshbochu wants to merge 1 commit intoanomalyco:devfrom
joshbochu wants to merge 1 commit intoanomalyco:devfrom
Conversation
This was referenced Apr 26, 2026
Bojun-Vvibe
added a commit
to Bojun-Vvibe/oss-contributions
that referenced
this pull request
Apr 26, 2026
- anomalyco/opencode#24411: structured-vs-string reasoning_details split for Kilo - anomalyco/opencode#24412: startup-stdin side-buffer drain into TUI prompt - openai/codex#19620: AsciiJsonFormatter for HTTP turn-metadata headers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Closes #24410
Type of change
What does this PR do?
Kilo/Kimi K2.6 can receive invalid request bodies when prior assistant reasoning is converted into a plain string
reasoning_detailsfield. This keeps plain reasoning text out ofreasoning_detailsand only preserves that field when structured details already exist.How did you verify your code works?
bun test test/provider/transform.test.tsbun typecheckScreenshots / recordings
Not a UI change.
Checklist