Codex Desktop
Best for Codex desktop users. CC Switch is the simplest setup; manual Responses configuration is also shown.
Protocol: OpenAI Responses. Base URL: https://openbulu.com/v1. Endpoint: POST /v1/responses.
Configuration example
model = "<MODEL_ID>"
model_provider = "openbulu"
[model_providers.openbulu]
name = "OpenBulu"
base_url = "https://openbulu.com/v1"
env_key = "OPENBULU_API_KEY"
wire_api = "responses"
requires_openai_auth = false
supports_websockets = falseExamples use placeholders only. Keep your real API key in an environment variable or the client’s secure credential store.
Setup steps
- For the simplest setup, install CC Switch and create an OpenBulu Codex provider; manual config is also supported.
- For manual setup, edit %USERPROFILE%\.codex\config.toml on Windows or ~/.codex/config.toml on macOS. Set model, model_provider, Base URL, env_key, and wire_api as shown. Keep OPENBULU_API_KEY in your user environment, not in this file.
- If using CC Switch, activate the imported provider. Fully quit and reopen Codex Desktop, start a new task, then send the test prompt.
Verify setup
Create a key, choose a model available to your account, run a small request in the client, then check its model, result, and charge in Usage Logs. Do not share the full key.
A new Codex Desktop task returns the requested sentence; a matching OpenBulu usage log shows /v1/responses and the selected model.
Troubleshooting
- Restart Codex Desktop after changing providers so it reloads config.toml and environment variables.
- If an existing task still calls api.openai.com after a provider switch, start a new task before judging the OpenBulu key.
- A short reply checks basic connectivity only. Verify streaming in the usage log and test file tools with a separate task in a disposable folder.