[BUG] Cerebras API is not accessible.

[seeseei]

Problem (one or two sentences)

Roo IDE can’t connect to the Cerebras API. It works fine in other IDEs, but only Roo can’t connect.

Context (who is affected and when)

Roo IDE can’t connect to the Cerebras API. It works fine in other IDEs, but only Roo can’t connect.

Reproduction steps

Roo IDE can’t connect to the Cerebras API. It works fine in other IDEs, but only Roo can’t connect.

Expected result

Roo IDE can’t connect to the Cerebras API. It works fine in other IDEs, but only Roo can’t connect.

Actual result

Roo IDE can’t connect to the Cerebras API. It works fine in other IDEs, but only Roo can’t connect.

Variations tried (optional)

Roo IDE can’t connect to the Cerebras API. It works fine in other IDEs, but only Roo can’t connect.

App Version

Version: 3.36.14 (2ca6f5f)

API Provider (optional)

Not Applicable / Other

Model Used (optional)

cerebras glm4.6

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

Thanks for reporting this issue. To help diagnose the Cerebras API connection problem, I need some additional information:

1. What error message do you see? When you try to connect to Cerebras, does Roo Code display any specific error message (e.g., authentication failed, rate limit exceeded, server error, timeout, etc.)?

2. Which model are you selecting in Roo Code? I see Roo Code has these Cerebras models available:

   • zai-glm-4.6
   • qwen-3-235b-a22b-instruct-2507
   • llama-3.3-70b
   • qwen-3-32b
   • gpt-oss-120b

   You mentioned "cerebras glm4.6" - are you selecting zai-glm-4.6 from the model list?

3. Can you check the Output panel? In VS Code, go to View > Output and select "Roo Code" from the dropdown. Are there any error messages logged there when you attempt to use Cerebras?

4. What other IDEs work with your Cerebras API key? This will help determine if the issue is specific to the API format Roo Code uses.

5. Are you using any proxy or VPN? Network configuration can sometimes affect API connectivity.

Please tag @roomote in your response with the answers, and I will propose a fix once I have this information.

[seeseei]

API Error Docs Unknown API error. Please contact Roo Code support.

…

-----Original Message----- From: ***@***.***> To: ***@***.***>; Cc: ***@***.***>; ***@***.***>; Sent: 2025-12-20 (토) 02:41:43 (GMT+09:00) Subject: Re: [RooCodeInc/Roo-Code] [BUG] Cerebras API is not accessible. (Issue #10212) roomote[bot] left a comment (RooCodeInc/Roo-Code#10212) Thanks for reporting this issue. To help diagnose the Cerebras API connection problem, I need some additional information: What error message do you see? API Error Docs Unknown API error. Please contact Roo Code support. Which model are you selecting in Roo Code? I see Roo Code has these Cerebras models available: zai-glm-4.6 You mentioned "cerebras glm4.6" - are you selecting zai-glm-4.6 from the model list? Can you check the Output panel? VS Code No Error What other IDEs work with your Cerebras API key? cline, kilo Are you using any proxy or VPN? no Please tag @roomote in your response with the answers, and I will propose a fix once I have this information. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

Thanks for providing the additional details. I have seen your comment and will explore a potential fix.

Based on my investigation, the issue appears to be related to how error messages from the Cerebras API are being propagated to the UI. The "Unknown API error" message appears when the error does not include the HTTP status code in a format the frontend can parse.

I will open a PR to address this issue. Stay tuned!

@seeseei I've opened a PR with my attempt at addressing this issue: #10231

The root cause was that the Cerebras provider was throwing errors without attaching the HTTP status code, which the UI needs to display the appropriate error message. Without the status, it defaults to showing "Unknown API error."

The fix attaches HTTP status codes to all errors thrown by the Cerebras provider, so you should see the actual error message (authentication failed, rate limit exceeded, etc.) instead of the generic unknown error.

Feedback welcome!