Feature Request? Better tools & workflows to keep ~/.codex/config.toml in sync with new releases (without manual doc scraping)

[PanagiotisC00]

Problem

Codex CLI evolves fast — new MCP server options, multi-agent roles, sandbox policies, profiles, feature flags, web-search modes, shell environment tweaks, UI behaviors, and more land in almost every minor release.

My ~/.codex/config.toml is the single source of truth for all that power, but keeping it current feels manual and inefficient:

• I have to visit Config Basics, Advanced Config, Configuration Reference, and the sample.
• Copy-paste large sections as Markdown.
• Feed them to an LLM with my current file and ask “what’s new or changed?”
• Manually decide what to add, comment out, or migrate.

This works, but it’s fragile, time-consuming, and I’m sure I miss useful tunables (or deprecated warnings) until something feels off. It’s especially painful for power users who maintain complex setups across machines, profiles, or shared team configs.

Gaps

A first-class, official, low-friction way to discover and adopt new options without leaving the terminal or doing web scraping.

Proposed improvements (pick any/all)

1. CLI-native config management commands (highest impact)

codex config status          # → "You are 2 releases behind on new options; here’s what’s missing"
codex config upgrade         # → diff vs latest defaults/schema, interactive add/comment new keys
codex config template --full # → outputs fully commented reference with current version
codex config doctor          # → validates, warns on deprecated keys, suggests secure defaults
codex config diff v0.102..v0.104  # → shows exactly what changed in config surface

Question

Does a way already exist to do what Im having trouble with. If yes then what is it? (and apologies for not noticing it). If no, then are there plans for this?

[etraut-openai]

If you'd like to suggest a new feature, please open a feature request in our feature tracker. We generally prioritize features based on community upvotes.

I help maintain the official documentation for Codex, and I struggle to keep up with the changes in the CLI code base. I relying on Codex to help with this. That's potentially a solution you might want to consider as well. Just create a skill that pulls the latest codex sources and/or looks at the latest codex documentation and examines your config file for any potential out-of-date details.