Repository navigation
feat(models): declare reasoning efforts for glm-5.2 on bytedance - #3138
Merged
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe ByteDance provider mapping for ChangesGLM-5.2 reasoning effort configuration
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Jul 19, 2026
This was referenced Aug 2, 2026
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.
Summary
Declares
reasoningEffortsforglm-5.2onproviderId: "bytedance"inpackages/models/src/models/zai.ts.Changes
glm-5.2(bytedance,glm-5-2-260617) →["none", "minimal", "low", "medium", "high", "xhigh", "max"]Source
Volcengine Chat API reference (Chinese docs).
glm-5-2-260617is the one model explicitly named on Volcengine's allowlist for the full tier range:noneandxhigh: restricted toglm-5-2-260617only.max: allowed forglm-5-2-260617,deepseek-v4-pro-260425,deepseek-v4-flash-260425.minimal/low/medium/high: documented without model restriction.Combined, this gives the full 7-tier ladder for this specific model/host — directly confirmed, not inferred.
Not changed
glm-5.2hosts checked but excluded:canopywaveandgranite(no documented reasoning-control parameter at all),embercloud(thereasoning.effortparameter exists in their docs, but no accepted values are published — nothing concrete to cite).Testing
pnpm format— clean, onlyzai.tschanged (array wrapped across multiple lines by the formatter).Summary by CodeRabbit