Cmd. /debug-config
Inspect Codex config layers, policy sources, and requirements diagnostics.
Key takeaways
- Inspect Codex config layers, policy sources, and requirements diagnostics.
- Check the input surface and availability before using the examples below.
Purpose
Inspect Codex config layers, policy sources, and requirements diagnostics.
/debug-configAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
The installed command menu and account or organization settings determine availability.
Examples
/debug-configWhen to use it
- Run
/debug-configwhenconfig.tomldoes not appear to match runtime behavior. - Use it before changing managed or project-scoped configuration.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/debug-config | Explains config layers and policy sources | You need root-cause diagnostics |
/status | Shows current session state | You need a quick snapshot |
/permissions | Changes approval policy | You need to adjust behavior |
Effects and persistence
Displays effective configuration and its sources without editing configuration files.
/debug-config prints configuration layer diagnostics and policy details, including approval
policies, sandbox modes, MCP servers, rules, residency, and experimental network settings.
to v0.139.0 Changes
/debug-configcan show effective sandbox modes more clearly, which helps explain runtime behavior across config, managed requirements, and sandbox helpers.codex sandbox -P <profile>adds a shorter permissions-profile alias for validating named permission profiles through the sandbox helper.- Network proxy enforcement now matters inside the sandbox path, so teams should verify proxy policy with both
/debug-configand a real sandbox run.
Cautions
- Diagnostics may expose paths or policy details; share output carefully.
- Do not change managed policy locally without understanding ownership.
Official sources
Complete command list · Verification scope · History for this command