[ENHANCEMENT] Support for Chutes.ai GLM-5 Model

[IanDaley]

Problem (one or two sentences)

Chutes have just added support GLM-5

https://chutes.ai/app/chute/e51e818e-fa63-570d-9f68-49d7d1b4d12f

Can we ensure this model is available, tested and working through RooCode please.

Context (who is affected and when)

All Chutes.ai users could benefit.

Desired behavior (conceptual, not technical)

GLM-5-TEE model is available for selection for Chutes provider.
GLM-5-TEE is confirmed tested and working for users.

Constraints / preferences (optional)

No response

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)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I have looked into this and wanted to share some context that affects the feasibility of this request.

The Chutes.ai provider was retired from Roo Code just a few days ago in PR #11297. That PR removed 9 low-usage providers (including Chutes, Cerebras, DeepInfra, Groq, and others) to reduce the maintenance surface of the codebase. The Chutes provider is now in the retiredProviderNames list, and users who had it configured see a "provider no longer supported" message.

Because of this, adding GLM-5-TEE as a built-in model for the Chutes provider is not possible without reversing the retirement decision, which is outside the scope of a single model addition.

Workaround available today: You can still use Chutes.ai (and GLM-5-TEE) through the OpenAI Compatible provider in Roo Code. Since Chutes exposes an OpenAI-compatible API, you can:

1. Select the OpenAI Compatible provider in Settings
2. Set the Base URL to the Chutes API endpoint (e.g. https://chutes.ai/api/v1)
3. Enter your Chutes API key
4. Type in the model ID for GLM-5-TEE manually

This gives you full access to any model Chutes offers, including GLM-5-TEE, without needing a dedicated provider integration.

If the maintainers would like to explore a different direction here (e.g. un-retiring Chutes or adding GLM-5-TEE through another active provider), please mention @roomote in a comment and I will be happy to implement it.

[IanDaley]

Oh that's very disappointing, especially since they were a big promoter of Roo in the early days.