feat(openai): Add Config Option to Overwrite OpenAI's API Base

[GOODBOY008]

Context

Add Config Option to Overwrite OpenAI's API Base #3052

Description:

It would be beneficial to add a configuration option that allows users to overwrite the OpenAI API base.

Use Case:

Users facing issues with OpenAI's regional restrictions, where the default API base may not be accessible due to geo-blocking or other limitations.

Screenshots

before	after

|

How to Test

Get in Touch

---

Important

Adds openAiNativeBaseUrl configuration option to overwrite OpenAI's API base URL, updating relevant schemas, models, and UI components.

• Behavior:
  • Adds openAiNativeBaseUrl to providerSettingsSchema in roo-code.ts and schemas/index.ts.
  • Updates OpenAiNativeHandler in openai-native.ts to use openAiNativeBaseUrl for API client initialization.
  • Updates ApiOptions in ApiOptions.tsx to include a text field for openAiNativeBaseUrl when openai-native is selected.
• Models:
  • Adds openAiNativeBaseUrl to ProviderSettings in roo-code.d.ts and types.ts.
• Misc:
  • Updates providerSettingsRecord in roo-code.ts and schemas/index.ts to include openAiNativeBaseUrl.

^{This description was created by for b3c7be7. You can customize this summary. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 94ead25

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

For the openai-native provider, the text field uses the translation key settings:providers.openAiBaseUrl which is also used by the regular OpenAI provider. Consider using a more specific key (e.g., settings:providers.openAiNativeBaseUrl) to clearly differentiate the native API base URL from the standard one.

Suggested change

	<label className="block font-medium mb-1">{t("settings:providers.openAiBaseUrl")}</label>
	<label className="block font-medium mb-1">{t("settings:providers.openAiNativeBaseUrl")}</label>

^{This comment was generated because it violated a code review rule: mrule_JLtLS6tLppVEv8iV.}

[mrubens]

Can we make this behind a checkbox like we do for Anthropic, OpenRouter, etc?

[GOODBOY008]

Okay, I believe it will be more user-friendly.

[jerilseb]

There is an API Provider name 'OpenAI Compatible' which allows custom base URL. Doesn't that solve this use case?

[mrubens]

There is an API Provider name 'OpenAI Compatible' which allows custom base URL. Doesn't that solve this use case?

I don't want to speak for @GOODBOY008, but in some cases it's hard to support different native OpenAI models like o1, o3, and o4-mini with the checkboxes that are provided in the OpenAI-compatible provider.

[mrubens]

Looks good, thanks!