ISSUE DESCRIPTION Stale 'clientversion' fallback causes 503 'noplansupportformodel' for…
- User
ISSUE DESCRIPTION
Stale 'client_version' fallback causes 503 'no_plan_support_for_model' for newer models (e.g. gpt-5.5) when GitHub releases API rate-limits
Summary
When
app/core/clients/codex_version.pycannot fetch the latest codex release fromapi.github.com/repos/openai/codex/releases/latest(e.g. anonymous-rate-limited with HTTP 403), it logs:GitHub releases API returned HTTP 403 GitHub fetch failed and no cached version; falling back to settings default 0.101.0and falls back to
Settings.model_registry_client_version(default0.101.0). The model registry refresh (app/core/openai/model_refresh_scheduler.py→clients/model_fetcher.fetch_models_for_plan) then asks upstream/codex/models?client_version=0.101.0. Upstream gates newer model slugs behind newer client versions, so the response excludes e.g.gpt-5.5.As a result,
ModelRegistry.model_plansnever gets agpt-5.5entry,_filter_accounts_for_modelinmodules/proxy/load_balancer.py:1168returns an empty set, and every Codex request forgpt-5.5is rejected with:proxy_error_response status=503 code=no_plan_support_for_model message=No accounts with a plan supporting model 'gpt-5.5'…even though the actual Codex CLI is on
0.130.0and the account's ChatGPT subscription does support the model (calling/backend-api/codex/models?client_version=0.130.0through the LB returns 200 with the model present).Reproduction
- Run
ghcr.io/soju06/codex-lb:1.17.0on a host where anonymous GitHub API requests are 403'ed. - Connect a current Codex CLI (e.g.
@openai/codex@0.130.0) configured withmodel = \"gpt-5.5\". - Observe startup log line:
GitHub fetch failed and no cached version; falling back to settings default 0.101.0
- Every
POST /backend-api/codex/responsesreturns 503 with codeno_plan_support_for_model.
Setting
CODEX_LB_MODEL_REGISTRY_CLIENT_VERSION=0.130.0and recreating the container fully resolves the symptom.Suggested fixes
A few low-effort options, any one would help:
- Bump the baked-in default
model_registry_client_versionon each release so it tracks the recent@openai/codexversion (or read it from a generated file at build time). - Add a secondary version source.
npm view @openai/codex versionagainsthttps://registry.npmjs.orgis not rate-limited the way the GitHub anonymous API is, and a static fetch ofhttps://registry.npmjs.org/@openai/codex/latestreturns JSON containing\"version\". - Cache the fetched version on disk (e.g. inside the data volume) so a single successful lookup survives container restarts and survives transient 403s for the cache TTL.
- Honor the client's own
client_versionquery string as a hint for which model list to refresh (only when greater than the configured default), so a newer client effectively bootstraps the registry.
Workaround
For anyone hitting this, pass
-e CODEX_LB_MODEL_REGISTRY_CLIENT_VERSION=<your-codex-cli-version>todocker run:docker run -d \\ -e CODEX_LB_DASHBOARD_BOOTSTRAP_TOKEN=... \\ -e CODEX_LB_MODEL_REGISTRY_CLIENT_VERSION=0.130.0 \\ -p 2455:2455 -p 1455:1455 \\ -v codex-lb-data:/var/lib/codex-lb \\ ghcr.io/soju06/codex-lb:1.17.0Environment
- codex-lb image:
ghcr.io/soju06/codex-lb:1.17.0 - Codex CLI:
@openai/codex@0.130.0 - Host: macOS, Docker Desktop / Colima
- Account plan:
pro(3 accounts, allplan_type=proinstore.db)
Related: #480 ("Model metadata for
gpt-5.5not found. Defaulting to fallback metadata") looks like the same underlying cause.ADDITIONAL ADVICE
Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use
git checkout <file>to restore the file to its original state. You can also reset all changes in the repository usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto get the changes that need to be submitted.CHECKLIST
Before submitting your solution, please go over the following checklist and make sure you've done everything:
- If an error was reported in the issue description, I have successfully reproduced it.
- If an error was reported in the issue description, I have confirmed that my fix resolves the error.
- I have thought about edge cases and made sure my fix handles them as well.
- I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
(Current directory: /codex-lb, current file: none) bash-$
- Run
Assistant
I'll start by exploring the repository structure to understand the codebase and then locate the relevant files mentioned in the issue.
Assistant
Let me explore the directory structure more systematically.
Assistant
Now let me look at the key files mentioned in the issue:
Assistant
I need to use the proper syntax for opening a file.
Assistant
Now let me look at the model refresh scheduler and model fetcher:
Assistant
Now I understand the issue. Let me check the tests to understand how the existing code is tested:
Assistant
Now I have a clear understanding of the issue. Let me check what the NPM registry approach would look like and then implement a fix. The issue suggests several approaches - I'll implement option 2 (secondary version source from NPM registry) as it provides a robust fallback:
Assistant
Let me continue working on the fix. I'll implement the NPM registry fallback as suggested in the issue.
Assistant
Now let me create a reproduction script to understand the issue better, then implement the fix:
Assistant
I need to use the virtual environment that's set up in the repository.
Assistant
I've confirmed the issue. Now let me implement the fix. According to the issue, I'll implement option 2: add a secondary version source using the NPM registry. This is a good approach because:
- The NPM registry (
https://registry.npmjs.org) is less likely to be rate-limited - It provides the latest published version of
@openai/codex - It's a static JSON endpoint that's easy to parse
Let me implement the fix:
- The NPM registry (
Assistant
Now I'll implement the fix by adding an NPM registry fallback. The strategy is:
- First try GitHub releases API (existing behavior)
- If GitHub fails, try the NPM registry as a secondary source
- If both fail, fall back to stale cache or settings default
Assistant
Now let me run the reproduction script again to verify the fix works:
Assistant
All my tests pass. Now let me run the existing unit tests to make sure I haven't broken anything:
Assistant
All existing tests pass. Let me also check if there are any tests related to the model fetcher that might be affected:
Assistant
All related tests pass. Let me also run the full test suite to make sure nothing else is broken:
Assistant
I need to continue checking the test results to see if all tests pass.
Assistant
All 1889 unit tests pass (with 39 skipped that are expected). Now let me verify the file I modified looks correct:
Assistant
Let me also think about edge cases and add more comprehensive tests:
Assistant
All edge case tests pass. Now let me clean up the temporary test files and verify the git diff:
Assistant
Let me run the existing unit tests one more time to confirm everything passes:
<tool_call> <function=bash_terminal> <parameter=command> cd /codex-lb && .venv/bin/python -m pytest tests/unit/test_codex_version.py tests/unit/test_model_fetcher.py tests/unit/test_model_refresh_scheduler.py -v </tool_call>
Assistant
I need to run the command properly.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →