codex - 💡(How to fix) Fix Interactive TUI Installer for Multiple Custom Model Providers [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17801Fetched 2026-04-15 06:27:58
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×5commented ×1unlabeled ×1
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

CLI

What feature would you like to see?

Problem statement: Setting up Codex with multiple models/providers (e.g., OpenRouter) currently requires:

Manually editing ~/.codex/config.toml Managing multiple environment variables in shell config (.zshrc, .bashrc) Understanding internal concepts like model_provider, env_key, etc.

This creates significant friction, especially for:

New users Multi-model workflows Cost tracking setups, etc..

Proposed Feature:

Add an interactive installer/setup flow inside the Codex TUI to configure models and providers.

Where user will provide the model name, URL Link, api key written in a file(optional), the installer will manually update the config.toml, create aliases (ex: alias codex-gpt='codex -c model="openai/gpt-5.4" -c model_provider="openrouter_gpt"' alias codex-glm='codex -c model="z-ai/glm-5.1" -c model_provider="openrouter_glm"' ), test connection.

Users will init different sessions as per their need.

Codex already has powerful support for:

custom providers multiple models flexible config

But lacks a guided UX layer.

A TUI installer would make these capabilities easily accessible.

Additional information

I have already created a installer script for my local setup

extent analysis

TL;DR

Implementing an interactive installer/setup flow in the Codex TUI can simplify the configuration of multiple models and providers.

Guidance

  • Consider creating a user-friendly interface to collect model names, URLs, and API keys, which can then be used to update the config.toml file.
  • Develop a system to automatically create aliases for different models and providers, similar to the proposed codex-gpt and codex-glm examples.
  • Integrate a connection testing feature to ensure the configured models and providers are working as expected.
  • Review the existing config.toml file structure and update it to accommodate the new installer flow, if necessary.

Example

# Example alias creation
alias codex-gpt='codex -c model="openai/gpt-5.4" -c model_provider="openrouter_gpt"'
alias codex-glm='codex -c model="z-ai/glm-5.1" -c model_provider="openrouter_glm"'

Notes

The proposed feature aims to improve the user experience by providing a guided setup flow, but it may require significant changes to the existing Codex TUI and configuration management.

Recommendation

Apply workaround: Utilize the existing config.toml file and manually create aliases for different models and providers until the interactive installer is implemented. This will allow users to still leverage the powerful features of Codex while waiting for the improved UX layer.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Interactive TUI Installer for Multiple Custom Model Providers [1 comments, 2 participants]