What changed in Codex CLI v0.168 and v0.169, and when codex exec needs --trust
In v0.169.0 codex exec stops loading an untrusted project's configuration. Here is how --trust works, and which config keys from the release notes are missing from the reference.
Contents
Codex CLI v0.168.0 and v0.169.0 carry one change that matters for CI: codex exec no longer loads configuration or MCP servers from a project you have not trusted.
There is a second thing worth knowing before you edit any config. Of the settings keys named in these release notes, three are absent from the official configuration reference, and one has a documented value list that contradicts the notes. It is worth sorting the verified from the unverified first.
KEY POINT
What you will learn
- What the
codex exectrust check disables, and when to pass--trust - Setting project trust in a file with
projects.<path>.trust_level - Which release-note keys cannot be confirmed against the configuration reference
codex exec ignores an untrusted project's configuration
The first v0.169.0 bug fix reads:
codex execkeeps project configuration and MCP servers disabled in untrusted directories, even with--sandbox workspace-write. Use--trustwithcodex execorcodex reviewto explicitly save project trust.
Widening the sandbox does not widen trust. The configuration reference states the premise: "Codex loads project-scoped config files only when you trust the project."
What untrusted actually turns off is spelled out in Advanced Configuration:
If the project is untrusted, Codex ignores project
.codex/layers, including.codex/config.toml, project-local hooks,
and project-local rules. User-level and system-level layers are separate and keep loading. For hooks specifically: "Project-local hooks load only when the project .codex/ layer is trusted." and "User-level hooks remain independent of project trust."
Here is the flag:
# Save this project's trust for this run and for future chats
codex exec --trust "Run the test suite and summarize failures"
Save project trust for this run and future chats, even with
--ephemeral. Conflicts with--ignore-user-config.
So trust is saved even when you pass --ephemeral (which keeps session rollout files off disk), and it cannot be combined with --ignore-user-config. On the review side, codex review --trust is documented as "Trust this project for this review and future chats, including its configured MCP servers."
The MCP part could not be confirmed in the configuration reference
The release notes say MCP servers stay disabled too. But no statement that an untrusted project's MCP servers do not load could be found in the configuration reference or Advanced Configuration. What those pages list as the consequences of being untrusted stops at the project .codex/ layers: project config, project-local hooks, project-local rules. The wording of codex review --trust, "including its configured MCP servers", is the only text pointing that way.
You can also declare trust ahead of time.
| Key | Values | What the docs say |
|---|---|---|
projects.<path>.trust_level | "trusted" / "untrusted" | "Mark a project or worktree as trusted or untrusted". An untrusted project will "skip project-scoped .codex/ layers, including project-local config, hooks, and rules" |
Do not confuse this with approval_policy = "untrusted", which is gone. The reference says "Codex and ChatGPT Work no longer support approval_policy = \"untrusted\"" while noting that "Project entries with trust_level = \"untrusted\" in user-level ~/.codex/config.toml remain supported." For that distinction, see Stop Codex asking whether to trust this folder with trust_level in config.toml.
Release-note keys that are missing from the reference
The v0.168.0 notes name three configuration keys. Checked against the configuration reference as of 2026-11-18:
| What the release notes say | What the reference says |
|---|---|
features.tui_workspace (a side conversation beside the main chat) | No entry for the key. The name appears once, inside the /side slash-command description |
features.image_generation_animation (animated GIF generation) | No entry |
tui.notification_method = "osc777" | The key exists, but its values are auto, osc9 and bel — there is no osc777 |
incremental_tools_legacy_gcp (v0.167.2) | No entry |
The documented description of tui.notification_method is "Notification method for terminal notifications (default: auto)." auto is explained too: Codex prefers OSC 9 where the terminal looks capable and "falls back to BEL (\x07) otherwise." Related keys are tui.notification_condition (unfocused / always, default unfocused) and tui.notifications.
So if you want to change the notification method, osc9 and bel are what you can verify today. osc777 exists only in the release notes. For the file as a whole, see How to write Codex config.toml and its main settings keys.
The features.multi_agent deprecation is not in the docs
One v0.168.0 chore reads:
Codex warns when
features.multi_agentis explicitly configured and points toagents.enabledfor disabling subagent tools.
Both keys exist in the reference. But nothing marks features.multi_agent as deprecated.
| Key | Documented description |
|---|---|
features.multi_agent | "Enable multi-agent collaboration tools (spawn_agent, send_input, resume_agent, wait_agent, and close_agent)" plus "(stable; on by default)." |
agents.enabled | "Enable or disable multi-agent tools (default: true)." |
The same table does flag deprecation elsewhere: features.codex_hooks is called a deprecated alias of features.hooks, features.web_search a "Deprecated legacy toggle", and agents.max_threads a "Legacy alias" of agents.max_concurrent_threads_per_session. features.multi_agent carries none of those markers and is labelled stable.
Given that a warning now appears at startup, agents.enabled is the safer thing to write going forward. But which one is the official mechanism could not be confirmed in the official documentation.
The other changes
TUI additions:
- The side conversation supports multiple tabs, and saved local side chats reopen after a restart (v0.169.0)
- Turning on Collapse turn details in the full-screen transcript folds completed activity beneath each prompt, keeping answers visible and tool output searchable (v0.169.0)
Ctrl+Sin the terminal report editor saves a diagnostic ZIP locally, "even when uploads are disabled" (v0.169.0)- Model providers are browsable under Sessions → Model providers, where you pick the default for new chats (v0.168.0)
There is no documented leader key
Describing features.tui_workspace, the v0.168.0 notes say to "press leader z to zoom the focused pane". But no leader-key concept could be found in the official documentation. The documented binding syntax for tui.keymap.<context>.<action> uses normalized names such as ctrl-a, shift-enter, page-down and minus, with no prefix-sequence form.
Beyond the trust change, the fixes cover Windows sandbox handling for quoted cmd.exe paths, a terminal that stayed busy waiting on MCP servers a shared app server never reported, and interrupted turns not closing cleanly. For how approvals and sandboxing pair up, see Codex approval_policy versus sandbox_mode.
Summary
codex execdoes not read a project's configuration in an untrusted directory;--sandbox workspace-writedoes not change that, so pass--trust- To declare it in a file, set
projects.<path>.trust_levelto"trusted". This is not the retiredapproval_policy = "untrusted" features.tui_workspace,features.image_generation_animationandincremental_tools_legacy_gcphave no entry in the configuration referencetui.notification_methoddocumentsauto,osc9andbel;osc777is not among themfeatures.multi_agentnow warns at startup, but the reference does not mark it deprecated
FAQ
- My CI job stopped loading MCP servers under codex exec. What changed?
- v0.169.0. In an untrusted directory, project configuration and MCP servers stay disabled even with --sandbox workspace-write. Pass --trust to save project trust for that run and future chats.
- Can I set project trust in a config file instead?
- Yes. Set projects.<path>.trust_level to "trusted" or "untrusted". An untrusted project skips the project-scoped .codex/ layers, meaning project config, hooks and rules.
- Can I set tui.notification_method to osc777?
- The values documented in the configuration reference as of 2026-11-18 are auto, osc9 and bel. osc777 appears only in the v0.168.0 release notes.
Primary sources
This article was drafted by AI from official documentation and reviewed by the site operator before publishing. Found a mistake? Let us know via the contact page.