Does Codex config.toml not work after being changed? Troubleshooting by configuration priority

Codex config.toml changes that don't take effect usually don't mean the TOML file is corrupted, but because the configuration is overridden by higher priority, the project is not yet trusted, or the old session is still using startup settings. First, confirm which layer you are changing to, then continue investigating.

First, compare it with the actual configuration priority

Codex parses the same-name settings in the following order, from highest to lowest:

1. Current command parameters and -c key=value;
2. Within the project, .codex/config.toml load layer by layer from the root directory of the repository to the current directory, with values closest to the current directory prioritized;
3. --profile Selected personal configuration;
4. User Level ~/.codex/config.toml;
5. Unix system-level /etc/codex/config.toml;
6. Built-in default values.

For example, if the user specifies a sandbox_mode = "workspace-write" but the startup command has a --sandbox read-only, this operation must follow the command lines. The warehouse project configuration will override the user configuration.

Use one-time parameters to locate the configuration layer

First, temporarily overwrite the same setting with the command line. If the temporary value is valid, it means Codex supports this configuration, with issues focused on file location, priority, or trust status.

codex -c model_reasoning_effort="high"

Then, use strict configuration checks to make the current version directly report errors when encountering unfamiliar fields:

codex --strict-config

Function switches can be used to codex features list check the status of active status; The working directory and sandbox range are checked in sessions using /status.

When the project configuration is completely ignored, check the trust status

Untrusted projects do not load the .codex/ configuration layer within the project, which also includes project hooks and rules. At this point, user-level configurations will still load, so the common manifestation is "global settings work, warehouse settings are invalid." Confirm that the correct repository root directory is opened, then confirm the trusted directory through the startup prompt or /permissions.

Organized devices may also be subject to requirements.toml constraints. Sandbox or approval modes prohibited by administrators, personal configurations cannot be forcibly overridden; At this point, you should review your organizational strategy. Finally, open a new CLI session or reload the IDE extension, adjusting the position one at a time before verification.