feat(aihubmix): add longcat-2.0 - #7557
Merged
Merged
Conversation
Contributor
|
No actionable findings. |
github-actions
Bot
added
the
reviewer: ready
rekram1-node
enabled auto-merge (squash)
September 21, 2026 15:26
rekram1-node
disabled auto-merge
September 21, 2026 15:26
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.
Adds the missing AIHubMix route
longcat-2.0, inheriting lab metadata frommeituan/longcat-2.0and keeping only host-specific pricing, controls, and actual overrides.Sources:
providers/opencode-go/models/longcat-2.0.toml.Reasoning controls:
[{"type":"toggle"}]. AIHubMix is a multi-lab relay; exact request fields are recorded in the leading TOML comments.Toggle-only, matching the OpenCode Go peer and the AIHubMix catalog. No OpenRouter-specific budget is copied.
Validation:
bun validatepasses on this branch. Controls were checked against the published catalog and existing model/provider entries; no inference-effect claim is made from HTTP acceptance.