You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Auto-review uses invalid model name "codex-auto-review" #36094
For the DeepSeek endpoint in this report, you can keep your normal model
unchanged and route Codex's fixed codex-auto-review name to deepseek-v4-pro through a local gateway.
Install Swobu and create a codex
workspace with two explicit Responses routes:
Route
Backend model
Backend URL
deepseek-v4-pro
deepseek-v4-pro
your DeepSeek-compatible /v1 URL
codex-auto-review
deepseek-v4-pro
the same /v1 URL
Then point Codex at that workspace in ~/.codex/config.toml:
model = "deepseek-v4-pro"model_provider = "swobu"
[model_providers.swobu]
name = "Swobu"wire_api = "responses"base_url = "http://127.0.0.1:7926/c/codex/v1"
Codex does not need an API key for the loopback Swobu endpoint. Configure any
real backend credential on both Swobu targets.
I reproduced this route: Codex's model: "codex-auto-review" request reached
the backend as model: "deepseek-v4-pro".
This is a gateway workaround, not a Codex fix. The backend must support the
Responses behavior used by auto-review. It only addresses the model-name
rejection shown here; it does not repair other full-access or first-party
auto-review failures.
Disclosure: I maintain Swobu. If you try this on Desktop 26.721.41059, please
share whether the review request reaches DeepSeek. For a Swobu-specific failure,
include the error and backend setup at github.com/swobuforge/swobu, and I will
help investigate.
Activity
github-actions commentedon Jul 30, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
metrofun commentedon Jul 31, 2026
For the DeepSeek endpoint in this report, you can keep your normal model
unchanged and route Codex's fixed
codex-auto-reviewname todeepseek-v4-prothrough a local gateway.Install Swobu and create a
codexworkspace with two explicit Responses routes:
deepseek-v4-prodeepseek-v4-pro/v1URLcodex-auto-reviewdeepseek-v4-pro/v1URLThen point Codex at that workspace in
~/.codex/config.toml:Codex does not need an API key for the loopback Swobu endpoint. Configure any
real backend credential on both Swobu targets.
I reproduced this route: Codex's
model: "codex-auto-review"request reachedthe backend as
model: "deepseek-v4-pro".This is a gateway workaround, not a Codex fix. The backend must support the
Responses behavior used by auto-review. It only addresses the model-name
rejection shown here; it does not repair other full-access or first-party
auto-review failures.
Disclosure: I maintain Swobu. If you try this on Desktop 26.721.41059, please
share whether the review request reaches DeepSeek. For a Swobu-specific failure,
include the error and backend setup at
github.com/swobuforge/swobu, and I will
help investigate.