Update AIHubMix model metadata#1748
Open
EriDeLee wants to merge 1 commit intoanomalyco:devfrom
Open
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
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.
Summary
providermappings for GPT-series AIHubMix models so requests go through the AI SDK provider pathNotes
Some AIHubMix GPT-series requests currently fail through the AIHubMix backend because
max_tokenis not supported. Adding explicitprovidermappings lets these models route through the AI SDK-compatible path and avoids that backend-specific incompatibility.Note: I have not yet tested whether the
max_tokensissue is fully resolved after adding the provider mapping. I will perform testing after this PR is merged. If the problem persists, I will submit additional routing/split code to OpenCode.For Kimi K2.5 and K2.6, the previous metadata did not match the official capability descriptions. I updated these entries according to the official Kimi docs rather than copying capability values from other providers in the current database, since some existing Kimi K2.x entries appear inconsistent with the official model capabilities.
Validation
bun validatesuccessfully