Skip to content
CC Switch WikiUnofficial Community Wiki

The Codex Desktop UI project list is completely empty - Codex

Quick fix

CC Switch changed the model_provider key name. Set it back to custom, or upgrade. Lost official login and fewer reasoning tiers remain unresolved.

Symptom

Section titled “Symptom”
Error output
Codex Desktop UI 的项目列表完全为空
English translation

The Codex Desktop UI project list is completely empty

Cause

Section titled “Cause”

When switching some profiles (GPT, for example), CC Switch writes a non-custom value such as packycode into model_provider in ~/.codex/config.toml. Codex Desktop uses that field as the namespace filter key for its SQLite database, so a query for history threads matches 0 rows. Rewriting the config also causes other anomalies: supported_reasoning_levels not being fully preserved when generating cc-switch-model-catalog.json, degrading the reasoning tiers; local routing config not applying so requests reach the official endpoint directly and trigger a high demand error; and auth.json being unmodifiable so the official login entry point disappears.

Fix

Section titled “Fix”

  1. Upgrade CC Switch to a version containing commit b44f83f7, which fixed this so every third-party provider uses custom as the history bucket.

  2. If you cannot upgrade, change the provider key back to custom in the config file by hand or with a script before starting Codex.

    ~/.codex/config.toml
    model_provider = "packycode"
    model_provider = "custom"
    

    [model_providers.packycode]
    [model_providers.custom]

Affected Versions

Section titled “Affected Versions”
ToolCodex
VersionUnknown
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 4 real issues

FAQ

Section titled “FAQ”
Why does the project list come back immediately after switching to DeepSeek?
Because the DeepSeek profile writes custom as the model_provider value, matching the namespace the history was stored under, so the UI can query the history threads.
Does editing config.toml by hand affect which model is actually used?
No. As long as name, base_url, and the other real settings under [model_providers.custom] stay unchanged, Codex still calls the right model.
Section titled “Related problems”
No DEEPSEEK settings in the json config fileUpgrade cc-switch to v3.20.0+, tick the reasoning level in the model mapping and save again, to fix config not being written or overwritten by a template.6 issues merged<!-- Failed to upload "image.png" -->Screenshot upload failures do not affect the issue itself; please describe the error message in text.10 issues mergedIs codex no longer supported now that it became ChatGPT? - cc-switchUpgrade to cc-switch v3.17.0, which supports provider switching after Codex merged into ChatGPT Desktop, so old config is not overwritten.5 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.