opencode: Ensure non-empty reasoning content for interleaving#56182
Closed
raphaelluethy wants to merge 4 commits into
Closed
opencode: Ensure non-empty reasoning content for interleaving#56182raphaelluethy wants to merge 4 commits into
raphaelluethy wants to merge 4 commits into
Conversation
|
Thank you for this PR! I tried it and it's working perfectly now with OpenCode Go Kimi 2.6 and Deepseek v4 pro. |
Contributor
Author
|
They seemed to have updated the routing, I dont get the error anymore. I will therefore close the pr for now and will re-open it if needed. |
Contributor
|
I can confirm Kimi K2.6 through OpenCode Go now works without any issues 🎉 Thank you for letting us know @raphaelluethy! |
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
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.
Self-Review Checklist:
[ ] The content is consistent with the UI/UX checklistCloses #51743
I open this PR as an alternative to adding the fix in the global openai provider, as discussed in #55085
, as this seems to be an issue with the provider routing in opencode.
Release Notes: