-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Description
What specific problem does this solve?
In the Settings in the Provider section, when the user chooses the Chutes provider, the list of available models is outdated.
For the uses who want to use the latest and best Open Source coding models on the Chutes provider it looks like a Roo Code bug that these models aren't listed.
Root cause for the outdated list is that the model list is hardcoded in Roo Code, which is not ideal in a fast moving Open Source LLM market.
But anyway, I would propose to add these models to the list:
Qwen/Qwen3-Coder-480B-A35B-Instruct-FP8
zai-org/GLM-4.5-FP8
zai-org/GLM-4.5-Air
moonshotai/Kimi-K2-Instruct
moonshotai/Kimi-K2-Instruct
And if you would want to go this extra mile:
May I suggest dynamically reading the model list from:
http GET https://api.chutes.ai/chutes/?include_public=true&page=0&limit=25&include_schemas=false
(needs a Chutes API Key as a Bearer token auth header)
The list comes sorted descending by usage of the models, thus the first page of 25 models should suffice nicely for a dropdown in Roo Code, if you want to avaoid having rare/old/niche models in the list.
Additional context (optional)
No response
Roo Code Task Links (Optional)
No response
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear impact and context
Interested in implementing this?
- Yes, I'd like to help implement this feature
Implementation requirements
- I understand this needs approval before implementation begins
How should this be solved? (REQUIRED if contributing, optional otherwise)
No response
How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)
No response
Technical considerations (REQUIRED if contributing, optional otherwise)
No response
Trade-offs and risks (REQUIRED if contributing, optional otherwise)
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status