codex-configuration

Model profiles let you define named configurations in config.toml. Create profiles under the [profiles] section with model settings, then switch between them using codex -c or set your default profile. Each profile can specify different model parameters, sandbox modes, and approval policies tailored to your workflow.

Yes, use the codex -c flag to apply runtime overrides. Pass configuration keys as arguments like codex -c 'shell_environment_policy.inherit=all' to temporarily change settings without modifying your config file, useful for testing or quick adjustments.

Configure MCP servers in the [mcp_servers] section of config.toml. Specify server endpoints and their settings, then Codex integrates with them for automation tasks. Multiple servers can run concurrently across local, project, and repository scopes.

Configuration scopes control precedence: repository settings override project settings, which override local settings. Skills paths follow strict precedence rules. Use repository scope for team standards, project scope for workflow specifics, and local scope for personal preferences.

Configure sandbox_mode and approval policies in config.toml to control execution safety. Sandbox mode restricts file operations, while approval policies require consent before sensitive actions. Combine with exec_timeout_ms to set execution limits and control resource usage.

Check scope precedence—repository and project configs override local settings. Verify syntax in config.toml, confirm the file_opener and shell_environment_policy settings match your requirements, and use codex -c to test overrides. Review skills paths to ensure correct precedence order.