codex-doctor-debuggerlisted

# Codex Doctor And Debugger Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined (Claude Code: `PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"`), otherwise the absolute path of this plugin's root directory. Use this skill when Codex CLI itself is failing or unclear: installation, config, auth, runtime health, feature flags, sandbox denials, debug model catalog, app-server transports, remote-control daemon, remote connection errors, or local environment inconsistencies. If Codex starts normally, update-channel eligibility and freshness of a custom scheduled updater are outside this diagnostic lane. Inspect the updater that owns channel selection and use `scheduled-automation-runtime` to prove what its OS schedule actually ran. Return here only when Codex launch or runtime health itself is failing. ## Inspect First Start with cheap, non-mutating commands: ```bash python3 "$PLUGIN_ROOT/scripts/codex_cli_inspector.py" --commands doctor debug "debug prompt-input" sandbox features app-server remote-control --json codex doctor --summary --ascii ``` Use machine-readable doctor output when automation needs to classify issues: ```bash codex doctor --json ``` Do not paste raw doctor output into chat if it contains local paths, config fragments, or environment details that are not needed. Summarize issue names, counts, and actionable rows. ## Diagnostic Lanes ### Install,