Codex CLI presets: session settings are not defaults
A reusable prompt, a session setting and a default serve different purposes.
OpenAI’s October 23, 2026 release, 0.164.0, added ten numbered /presets slots and inline session controls. On November 2, GitHub lists 0.166.0, released October 29, as the latest stable build. Our later Codex coverage explains the intervening changes.
Choose the right place for the change
| Control | What it changes | Important boundary |
|---|---|---|
/presets | Reusable prompts or slash commands | Stored under tui.presets. Not a replacement for project context. |
/model arguments | Current model, reasoning and speed | Does not replace saved defaults or unlock unavailable choices. |
/permissions arguments | Selected permission profile | Required confirmation and policy restrictions still apply. |
| Configuration files | Defaults and project overrides | Higher-priority settings can override the value you edited. |
The preset, model and permission implementations document these boundaries. That release also fixed history lookup and settings restoration. Check active settings after resuming.
Why a saved default may not win
Current configuration documentation puts personal defaults in ~/.codex/config.toml and project overrides in .codex/config.toml. Project layers load only for trusted projects. Command-line overrides take precedence over project settings, followed by selected profiles, user configuration, cloud-managed defaults, system configuration and built-in defaults. Enforced requirements are separate from defaults.
For example, a team might want a common model default while one repository needs a narrower permission profile. Check which layer supplies each value before changing a global file. Do not loosen permissions merely to make two sessions look identical.
Access and cost are separate checks
As checked on November 2, 2026, OpenAI’s pricing page lists CLI access with Plus at $20 per month and Pro plans at $100, $200 or $500 per month, in USD. API-key usage is metered separately and follows the models available to that key. It does not include cloud features such as GitHub code review. Free and Go descriptions specify desktop access subject to rollout, so they are not evidence of equivalent CLI access. Check /status for remaining limits.
Use the official CLI installation guide, then try a disposable repository before bringing the workflow into important work. Create Git checkpoints around changes. ByteForward has not executed these builds or measured recovery reliability. The example above is suggested workflow, not a test result.
AI-generated conceptual editorial illustration by ByteForward, with the official OpenAI wordmark from its brand resources. Not a product screenshot. OpenAI owns its mark. No endorsement implied.
