Problem (one or two sentences)

The extension UI enforces a mandatory API Key for the LiteLLM provider, but LiteLLM supports and is often used without authentication in self-hosted or local environments.

Context (who is affected and when)

This affects users who host their own LiteLLM proxy (e.g., on a local network or private server) without an API Key configured. Currently, they cannot save the configuration or use the provider without entering a "dummy" key.

Reproduction steps

1. Open the Roo Code Settings page.
2. Select LiteLLM from the API Provider dropdown.
3. Enter a valid Base URL but leave the API Key field empty.
4. Observe that the UI marks the field as required and prevents the configuration from being active.

Expected result

The API Key field for LiteLLM should be optional. If left blank, the extension should send requests to the Base URL without an Authorization header.

Actual result

The UI validation forces a non-empty string for the API Key, making it impossible to use no-auth LiteLLM instances directly.

Variations tried (optional)

Entering a placeholder string (e.g., "none" or "dummy-key" or " ") does not works as a workaround.

App Version

3.51.1 (7c9722b)

API Provider (optional)

LiteLLM

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)