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 inspect the version-resolution code, settings, and relevant tests first. Then I’ll reproduce the fallback behavior, implement a resilient secondary source/cache-compatible fix following existing conventions, and run focused plus broader tests.
- Assistant
The current implementation has only an in-memory cache and treats any GitHub failure as final. I’ll inspect its unit tests and project configuration to determine the least invasive robust behavior; adding the npm registry as a secondary HTTP source directly addresses rate limiting without introducing persistence lifecycle concerns.
- Assistant
A focused baseline test confirms the reported path is already represented: an HTTP failure with no cache returns
0.101.0. I’ll now add npm’s package metadata endpoint as a true fallback for all GitHub failure modes (HTTP, malformed data, and transport errors), while retaining stale-cache and configured-default behavior if both independent sources fail. Each source gets its own session so a failed GitHub connection setup cannot prevent trying npm. - Assistant
The system Python lacks project dependencies, so the attempted reproduction could not execute. I’ll check the repository’s lockfile/package runner, implement the small source change, then use the project environment (installing locked dependencies if necessary) for verification.
- Assistant
The repository uses
uvand has a lockfile. I’ll update onlycodex_version.py: add the npm endpoint, isolate source fetches, validate npm’sversionexactly as GitHub’s release name, and improve fallback logs to accurately refer to both sources. - Assistant
The implementation is in place; lint found one formatting-only line-length violation. I’ll format that call, then run the existing unit suite. Existing tests intentionally mock only GitHub, so they also verify that malformed/unavailable npm data still preserves the original configured-default and stale-cache semantics.
- Assistant
The original tests pass. I’ll now explicitly reproduce the reported GitHub-403 scenario with npm returning a newer release and assert the selected version is the npm value. I’ll also test the edge case where GitHub session creation itself raises but npm succeeds, confirming source independence. Then I’ll inspect the diff and run type/lint plus the full unit suite.
- Assistant
The reproduction now selects
0.130.0after a simulated 403 and also succeeds after a transport exception. It exposed harmless duplicate “unexpected release” warnings after already-logged fetch failures; I’ll clean that up with an internal failure sentinel so malformed successful responses remain distinguishable from request failures, then run formatter, static checks, and all unit tests. - Assistant
All 1,889 runnable unit tests pass (39 environment/obsolete skips). The type checker found a generic-inference issue when narrowing JSON’s broad
objectreturn type to a dictionary; this is static only, but I’ll resolve it with explicitdict[str, object]casts, rerun all static checks and the focused tests, then perform final diff/status review.
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 →
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 →