Feature flags can explain why one Codex installation exposes a tool, permission flow, or experimental behavior that another installation does not. The feature list is a local read-only check that shows which flags the installed CLI knows and the effective state for the current invocation.
The installed CLI supplies the flag catalog, while its defaults and loaded configuration determine the effective values. The same project directory and shell environment as the session being diagnosed help keep the comparison meaningful.
A flag's maturity describes its lifecycle, not whether every related tool is available to an account. An installed Codex CLI can list flags without signing in or starting a model conversation.
Steps to list Codex feature flags:
- List the feature flags known to the installed Codex CLI.
$ codex features list agent_message_board under development false analytics_plan_history experimental false api_key_cyber_access_programs stable true api_key_model_discovery stable true app_server_websocket_compression under development false ##### snipped ##### workspace_dependencies stable true workspace_owner_usage_nudge removed false worktrees removed true write_stdin_approval stable true
The columns are feature key, maturity stage, and effective true or false state. Names, stages, and values can change between releases. An error instead of feature rows means the listing did not complete. A true value on a removed row does not restore the retired capability.
The stable stage identifies established features; experimental and under development identify features still being developed. deprecated and removed identify retired or retiring flags that may remain in the list. Listing flags does not write feature settings to config.toml.