[ENHANCEMENT] Add zai-org/GLM-4.5-turbo to Chutes API provider #8155
Description
Problem (one or two sentences)
Users cannot access the zai-org/GLM-4.5-turbo model through the Chutes API provider in Roo Code, limiting their ability to use this specific GLM model variant.
Context (who is affected and when)
Affects Chutes API users who want to use the zai-org/GLM-4.5-turbo model for coding tasks. This happens when users need access to this specific GLM model variant that's available through Chutes but not currently listed in Roo Code's model selection.
Desired behavior (conceptual, not technical)
Users should be able to select zai-org/GLM-4.5-turbo from the model list when using the Chutes API provider, with correct context window and pricing information displayed automatically.
Constraints / preferences (optional)
The model should be integrated following the same pattern as other Chutes models, maintaining existing authentication and configuration flows.
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear context and impact
Roo Code Task Links (optional)
No response
Acceptance criteria (optional)
Given I am using Chutes API provider in Roo Code settings When I view the available model list Then zai-org/GLM-4.5-turbo should appear as an available model option And the model should display correct context window information And pricing details should be
accurate And I can successfully select and use zai-org/GLM-4.5-turbo for coding tasks
Proposed approach (optional)
Follow the established pattern for adding models to the Chutes provider, similar to how other GLM models are integrated. This would involve updating the model configuration files and ensuring proper model metadata is included.
Trade-offs / risks (optional)
Should be minimal risk as this follows established patterns for adding new models to existing providers.