-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Closed as not planned
Closed as not planned
Copy link
Labels
Issue/PR - TriageNew issue. Needs quick review to confirm validity and assign labels.New issue. Needs quick review to confirm validity and assign labels.bugSomething isn't workingSomething isn't working
Description
App Version
3.27.0
API Provider
Chutes AI
Model Used
moonshotai/Kimi-K2-Instruct-0905
Roo Code Task Links (Optional)
Description
Roo Code 3.27.0 cannot complete requests when using:
- Provider = ChutesAI → always returns HTTP 500 (empty body)
- Provider = OpenAI-compatible (
https://llm.chutes.ai/v1) → returns HTTP 500 - Alternative base URL (
https://api.chutes.ai/v1) → returns HTTP 404
However, the identical request sent directly with curl succeeds every time:
curl -X POST https://llm.chutes.ai/v1/chat/completions \
-H "Authorization: Bearer <API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"model": "moonshotai/Kimi-K2-Instruct-0905",
"messages": [{ "role": "user", "content": "Hello." }],
"stream": false,
"max_tokens": 1024,
"temperature": 0.7
}'
App Version
Roo Code: 3.27.0 (VS Code extension)
VS Code: 1.89.1
OS: Ubuntu 22.04 LTS (x64)
Node.js: 22.18.0
Expected Behavior
Roo Code should return a normal chat completion, identical to the working curl request.
Actual Behavior
- Chutes AI provider: HTTP 500 with empty JSON body.
- OpenAI-compatible provider: HTTP 500 or 404 (depending on base URL).
No streaming, no content returned.
Logs / Console Output
info: Sending request to Chutes provider…
error: Request failed with status code 500
error: {}
Additional Context
- The integration bug looks identical to Issue Unexpected API response Problem with Chutes AI #7322 “Unexpected API response Problem with Chutes AI” which was marked fixed but still happens in 3.27.0[30].
- All quotas/credits on Chutes are valid; direct
curlconfirms the backend is healthy. - Re-installing the extension, clearing Roo Code cache, and disabling other extensions had no effect.
- OpenRouter BYOK works for other providers but is not an option here due to additional 5 % fee.
Request Checklist
- Searched existing Issues (Unexpected API response Problem with Chutes AI #7322) for duplicates.
- Provided clear steps to reproduce and logs.
- Confirmed the problem is on Roo Code’s side (direct API call works).
🔁 Steps to Reproduce
- Open Roo Code Settings → Providers → Chutes AI.
- Enter a valid API key and select
moonshotai/Kimi-K2-Instruct-0905. - Ask the model any question (e.g., “Hello”).
- Observe Request failed: 500 in Roo Code’s output panel.
- Switch to OpenAI-compatible provider with base URL
https://llm.chutes.ai/v1and repeat → same 500 error. - Try base URL
https://api.chutes.ai/v1→ Roo Code now shows 404.
💥 Outcome Summary
Expected code to run, but got an HTTP 500 with empty JSON body error.
📄 Relevant Logs or Errors (Optional)
Metadata
Metadata
Assignees
Labels
Issue/PR - TriageNew issue. Needs quick review to confirm validity and assign labels.New issue. Needs quick review to confirm validity and assign labels.bugSomething isn't workingSomething isn't working
Type
Projects
Status
Done