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
#5783 tracks LLM gateway support for the Codex CLI. Codex also ships a separate Desktop app (Electron, macOS/Windows only — no Linux) for supervising multiple agent threads. It's a distinct install/detection target from the CLI, so it needs its own client entry to be auto-detected and configured by thv llm setup, even though it largely shares config with the CLI.
What we know
Codex Desktop reads the same~/.codex/config.toml and ~/.codex/auth.json as Codex CLI — same custom model_providers config, same cached login. This is unlike Claude Desktop, which needed a dedicated credential-helper mode (pkg/clientModeCredentialHelper) because it uses a completely separate configLibrary document model.
Practically, this likely means:
Once Add Codex CLI support to thv llm setup #5783 lands (CLI direct-mode config.toml patching), Codex Desktop may work automatically since it reads the same file — this issue is partly about verifying that, not building a second write path.
Detection still needs its own client entry (distinct LLMDetectRelPath/binary check for the Desktop app bundle, since "is Codex Desktop installed" is a different check than "is the codex CLI binary on PATH").
Why
#5783 tracks LLM gateway support for the Codex CLI. Codex also ships a separate Desktop app (Electron, macOS/Windows only — no Linux) for supervising multiple agent threads. It's a distinct install/detection target from the CLI, so it needs its own client entry to be auto-detected and configured by
thv llm setup, even though it largely shares config with the CLI.What we know
Codex Desktop reads the same
~/.codex/config.tomland~/.codex/auth.jsonas Codex CLI — same custommodel_providersconfig, same cached login. This is unlike Claude Desktop, which needed a dedicatedcredential-helpermode (pkg/clientModeCredentialHelper) because it uses a completely separateconfigLibrarydocument model.Practically, this likely means:
config.tomlpatching), Codex Desktop may work automatically since it reads the same file — this issue is partly about verifying that, not building a second write path.LLMDetectRelPath/binary check for the Desktop app bundle, since "is Codex Desktop installed" is a different check than "is thecodexCLI binary on PATH").Known upstream caveats to account for
base_urlwith remote auth.json API key (openai/codex#24457) — when a local custom provider and a remote workspace are both configured, the Desktop app can send the wrong Authorization header. Worth a doc warning if we ship this before OpenAI fixes it.References