What version of the Codex App are you using (From “About Codex” dialog)?
v0.147.0
What subscription do you have?
Custom litellm provider
What platform is your computer?
AlmaLinux 10.2 (Lavender Lion)
What issue are you seeing?
After upgrading Codex from v0.146.0 to v0.147.0, all requests made through our LiteLLM-backed custom provider fail with the error: "We're currently experiencing high demand, which may cause temporary errors." The internal logs repeatedly show stream disconnected - retrying sampling request in codex_core::responses_retry until the maximum number of retries is reached. Downgrading to v0.146.0 immediately resolves the issue with no configuration changes. The same LiteLLM endpoint, credentials, models, and configuration work correctly on v0.146.0, which suggests a regression in v0.147.0, potentially related to streaming or Responses API handling with LiteLLM-compatible providers.
What steps can reproduce the bug?
- Configure Codex to use a LiteLLM-backed custom provider.
- Run Codex with
v0.147.0.
- Submit any prompt.
- The request fails after several retries with the
"high demand" error.
- Downgrade Codex to
v0.146.0 without changing the configuration.
- Submit the same prompt again.
- The request succeeds normally.
What is the expected behavior?
Requests should complete successfully with v0.147.0, using the same LiteLLM endpoint and configuration that work correctly with v0.146.0.
Additional information
I don't have access to the LiteLLM configuration, as it is managed through our corporate gateway. However, I can confirm that both gpt-5.6-luna and gpt-5.6-terra work correctly with other coding assistants using the same infrastructure, and they also work correctly with Codex v0.146.0.
The issue only appears after upgrading to Codex v0.147.0. Downgrading back to v0.146.0 immediately resolves it, which strongly indicates that the regression was introduced in v0.147.0.
Regression: v0.146.0 ✅ / v0.147.0 ❌
What version of the Codex App are you using (From “About Codex” dialog)?
v0.147.0
What subscription do you have?
Custom litellm provider
What platform is your computer?
AlmaLinux 10.2 (Lavender Lion)
What issue are you seeing?
After upgrading Codex from
v0.146.0tov0.147.0, all requests made through our LiteLLM-backed custom provider fail with the error: "We're currently experiencing high demand, which may cause temporary errors." The internal logs repeatedly showstream disconnected - retrying sampling requestincodex_core::responses_retryuntil the maximum number of retries is reached. Downgrading tov0.146.0immediately resolves the issue with no configuration changes. The same LiteLLM endpoint, credentials, models, and configuration work correctly onv0.146.0, which suggests a regression inv0.147.0, potentially related to streaming or Responses API handling with LiteLLM-compatible providers.What steps can reproduce the bug?
v0.147.0."high demand"error.v0.146.0without changing the configuration.What is the expected behavior?
Requests should complete successfully with
v0.147.0, using the same LiteLLM endpoint and configuration that work correctly withv0.146.0.Additional information
I don't have access to the LiteLLM configuration, as it is managed through our corporate gateway. However, I can confirm that both
gpt-5.6-lunaandgpt-5.6-terrawork correctly with other coding assistants using the same infrastructure, and they also work correctly with Codexv0.146.0.The issue only appears after upgrading to Codex
v0.147.0. Downgrading back tov0.146.0immediately resolves it, which strongly indicates that the regression was introduced inv0.147.0.Regression:
v0.146.0✅ /v0.147.0❌