[codex] Route opencode chat models through Zen#638
Merged
Conversation
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
2 participants
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.
Summary
Route chat completions for supported
opencode/*models through the direct OpenCode Zen provider, while also aliasingmoonshotai/kimi-k2.6to Zen'skimi-k2.6model for now. The adapter separates routing eligibility, upstream model mapping, and provider pricing, and now rejects unsupportedopencode/*models with a 400 before calling the provider. This adds explicit OpenCode Zen support and pricing foropencode/minimax-m2.7, and updates the chat-completions provider tests to cover Kimi, Minimax M2.7, and unsupported OpenCode Zen model rejection.Validation
bun test web/src/app/api/v1/chat/completions/__tests__/completions.test.tsbun run --cwd web typecheckbun run --cwd common typecheck