Answer: You can use the `RUST_LOG` environment variable to diagnose Codex issues, controlling Rust log filtering and verbosity. It accepts values such as `error`, `warn`, `info`, `debug`, and `trace`, as well as targeted filters like `codex_core=debug,codex_tui=debug`. Status: Confirmed Entry: tool/codex/troubleshooting/codex-diagnostics-env-vars Revision: 1 Digest: sha256:fced24eaec2267ed (changes whenever the content changes) Timeline: Created: 2026-11-13T03:48:27Z Last changed: 2026-11-13T03:48:27Z Last verified: 2026-11-20T13:36:07Z Next check: 2026-11-21T13:36:07Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Diagnostic variable | RUST_LOG | [1] | 2026-11-20 Accepted values | error | [1] | 2026-11-20 Targeted filter example | codex_core=debug,codex_tui=debug | [1] | 2026-11-20 Default exec output | error | [1] | 2026-11-20 Sources: [1] OpenAI. "Environment variables". https://learn.chatgpt.com/docs/config-file/environment-variables.md Role: primary. Accessed: 2026-11-20T13:36:07Z Quote: "| `RUST_LOG` | CLI and app-server | Controls Rust log filtering and verbosity." (Supports: Diagnostic variable) Quote: "`RUST_LOG` accepts values such as `error`, `warn`, `info`, `debug`, and" (Supports: Accepted values) Quote: "`codex_core=debug,codex_tui=debug`." (Supports: Targeted filter example) Quote: "`codex exec` defaults to `error` output unless you set a more verbose value." (Supports: Default exec output) Snapshot SHA-256: 091de0e9ff7f1c504549c2b7d8fe42cf8d1bd782f5a759d58bdead958f579ff8 (captured 2026-11-13T03:48:25Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:48:27Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:36:07Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:36:07Z Last attempt: 2026-11-20T13:36:07Z Notes and limitations: Extracted automatically from a single official source (section "Diagnostics"). Related: https://latestn.com/tool/codex/troubleshooting/deep-scan-interruption-failure What should I do if a Codex deep scan is interrupted or fails? https://latestn.com/tool/codex/troubleshooting/desktop-app-config-server-signin What are the limitations of the Codex desktop app when using a configuration server that requires sign-in? https://latestn.com/tool/codex/troubleshooting/exit-codes What exit codes does the Codex Security CLI return? https://latestn.com/tool/codex/settings/requirements-toml-location Where is the requirements.toml file located for Codex on Linux, macOS, and Windows? https://latestn.com/tool/codex/settings/set-reporting-thresholds How do I set reporting thresholds for Codex Security Review? https://latestn.com/tool/codex/settings/set-service-tier-per-turn How do I set the service tier for a single turn in the Codex SDK? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:48:27Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/troubleshooting/codex-diagnostics-env-vars/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/troubleshooting/codex-diagnostics-env-vars POST: https://latestn.com/dispute/tool/codex/troubleshooting/codex-diagnostics-env-vars with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/troubleshooting/codex-diagnostics-env-vars?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What environment variables can I use to diagnose Codex issues? Revision 1, last verified 2026-11-20T13:36:07Z. https://latestn.com/tool/codex/troubleshooting/codex-diagnostics-env-vars (accessed 2026-11-21T10:00:01Z). @misc{LatestN_tool_codex_troubleshooting_codex_diagnostics_env_vars_r1, title = {What environment variables can I use to diagnose Codex issues?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/troubleshooting/codex-diagnostics-env-vars}}, note = {Revision 1; digest sha256:fced24eaec2267ed; last verified 2026-11-20T13:36:07Z; accessed 2026-11-21T10:00:01Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/troubleshooting/codex-diagnostics-env-vars