Desktop: model_catalog_json loaded but custom models not shown in picker (regression, related to #32349)

Open
#34,487 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop

Research direction

Start with the custom provider configuration in ~/.codex/config.toml and compare the desktop model-picker path with the output of codex debug models. Reproduce using a catalog containing five entries with use_responses_lite: false; done means the desktop picker displays the configured custom models while API requests continue to work.

Written by the indexing model from the issue text.

Description

app bug config custom-model windows-os
What version of Codex?

Desktop 26.715.61943 / CLI 0.145.0-alpha.27 (Windows 11)

What issue are you seeing?

model_catalog_json is configured correctly, codex debug models shows all 5 custom models from the catalog JSON, but the desktop app model picker is completely empty when using a custom provider with env_key. The issue is the same as #32349 but also affects the desktop app, not just CLI.

  • config.toml has model_catalog_json pointing to a valid JSON file
  • codex debug models outputs all 5 models correctly
  • API requests work fine (provider: Volcengine CodingPlan via Responses API)
  • Desktop model picker dropdown is empty
Steps to reproduce
  1. Configure a custom provider with model_catalog_json in ~/.codex/config.toml
  2. The catalog JSON has use_responses_lite: false on every entry
  3. Open Codex desktop app
  4. Model picker dropdown is empty
Related
  • #32349 (same symptom on CLI)
Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.