[BUG] RooCode - OpenRouter & any new profile = 404

[Marcinszewski]

Problem (one or two sentences)

Openrouter not working with any new Configuration Profile, 404

Context (who is affected and when)

If I change the profile and add the Openrouter API, it can't connect. On the openrouter.ai website, the logs show that requests from chat aren't arriving, but they are arriving from indexing. If I use the standard default profile, the Openrouter API works perfectly on any model.

Reproduction steps

1. Add a new profile
2. Add the Openrouter API
3. Type "hello" in the chat
4. You receive various errors without a response

Expected result

Brak połączenia

Actual result

połączenie

Variations tried (optional)

No response

App Version

Version: 3.47.3 (ec2d110)

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

// Please share this file with Roo Code Support (support@roocode.com) to diagnose the issue faster
// Just make sure you're OK sharing the contents of the conversation below.

{
  "error": {
    "timestamp": "2026-02-10T07:41:13.507Z",
    "version": "3.47.3",
    "provider": "openrouter",
    "model": "qwen/qwen3-coder:free",
    "details": "Unexpected API Response: The language model did not provide any assistant messages. This may indicate an issue with the API or the model's output."
  },
  "history": [
    {
      "role": "user",
      "content": [
        {
          "type": "text",
          "text": "<user_message>\ntest\n</user_message>"
        },
        {
          "type": "text",
          "text": "<environment_details>\n# VSCode Visible Files\n..\\..\\..\\Users (clear...) t_details>"
        }
      ],
      "ts": 1770709265486
    }
  ]
}

Thanks for reporting this. I have been investigating the profile management and OpenRouter integration code paths and want to make sure I understand your exact workflow before proposing a fix.

I traced through ProviderSettingsManager.saveConfig(), activateProfile(), ClineProvider.upsertProviderProfile(), and the ContextProxy.setProviderSettings() flow. The code looks structurally correct for propagating OpenRouter settings (API key, model ID, base URL) from profiles to the API handler, but there are a few areas where a subtle issue could hide -- particularly around how secret keys (like openRouterApiKey) get cleared/set when switching profiles, and potential race conditions between saving a profile and starting a new task.

Could you help clarify the exact steps you follow? Specifically:

1. How do you create the new profile? Do you click the "+" button in the Configuration Profile section of Settings? When you do this, do you see the new profile appear in the dropdown?

2. How do you add the OpenRouter API to the new profile? Do you use the "Get API Key" OAuth button, or do you manually paste an API key? Do you also select a model from the model dropdown, or leave it as default?

3. Do you click "Save" after configuring the new profile with OpenRouter? And if so, do you get any confirmation or error in the UI?

4. After saving, do you immediately type "hello" in the chat, or do you do anything else in between? For example, do you switch tabs, reload VS Code, or switch to a different profile and back?

5. Is this reproducible with any OpenRouter model, or only with qwen/qwen3-coder:free? The error log mentions that specific model. Does it also fail with, say, anthropic/claude-sonnet-4 via OpenRouter?

6. Does this happen only with OpenRouter, or does creating a new profile with a different provider (e.g., Anthropic) also fail?

7. Could you share the Developer Tools console output (Help > Toggle Developer Tools) when the error occurs? There may be additional error messages or network request failures visible there that would help pinpoint the issue.

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