Codex App used with Azure hosted models

Open 💬 3 comments Opened Feb 27, 2026 by pmikolajczak

What version of the Codex App are you using (From “About Codex” dialog)?

26.226.940 (720)

What subscription do you have?

Azure models proxied via LiteLLM

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

I've set up the App to use our Azure models proxied via LiteLLM, works via

model = "gpt-5.3-codex"
model_provider = "litellm"
model_reasoning_effort = "high"

[model_providers.litellm]
name = "OpenAI"
base_url = "<redacted>"
wire_api = "responses"
env_key = "OPENAI_API_KEY"

in my ~/.codex/config.toml.

Two issues I see:

  • no model selection dropdown, no effort selection
  • CLI allows me switching between the models, if LiteLLM doesn't allow particular model for my key, usage of it simply errors out
  • agent does not resume work between turns, eg it does some exploration, writes the intermediate progress message and stops instead of continuing (the message clearly states the agent should continue).
  • prompting it to retry resumes work

What steps can reproduce the bug?

  • set up the App towards Azure/LiteLLM proxied models
  • no model or effort selection in the app
  • agent stops between turns

What is the expected behavior?

  • model and effort selection is available
  • agent can work without interruptions

Additional information

_No response_

View original on GitHub ↗

3 Comments

ilmarioranen · 5 months ago

Same issue here. Using Azure OpenAI with model_providers.azure in config.toml:

  • Codex App v26.317.21539 (1088), bundled codex-cli 0.116.0-alpha.1
  • macOS arm64
  • Model picker is completely empty — no model selection, no effort slider
  • New conversations still work (using the model from config.toml), but there is no way to switch models or adjust reasoning effort from the App UI

The bundled model catalog has models with visibility: list and supported_in_api: true (gpt-5.4, gpt-5.3-codex, etc.), and the cached models_cache.json includes them too. The backend build_available_models() should return them, so this appears to be a frontend/UI issue specific to non-ChatGPT auth modes.

Rafik-Belkadi-Reccap · 3 months ago

same here

FerjaniMY · 3 months ago

Same issue, any solutions ?