Codex CLI 0.169.0 Stops codex exec Loading Repo Config and MCP Servers in Untrusted Directories. CI Jobs Need --trust

OpenAI Codex logo(opens in new tab)OpenAI Codex(opens in new tab)ImportantNovember 17, 2026Coding Tools
What happened
Codex CLI 0.169.0 keeps project config and MCP servers off in untrusted directories for codex exec, even with workspace-write.
Why it matters
CI jobs in fresh checkouts that relied on repo config now run without it, and the release notes name no warning for that.
What to do
Add --trust to codex exec or codex review only where the repository's config should load.

This is the right fix, and it can change what some CI jobs do. In OpenAI Codex CLI 0.169.0, codex exec no longer loads a cloned repository's own project configuration or MCP servers in a directory you never trusted, even under --sandbox workspace-write. If your pipeline depends on that config, it now runs without it, and the release notes mention no warning or error when that happens. Our OpenAI Codex verdict stays recommended: this closes a hole rather than opening one.

What happened

The rust-v0.169.0 release notes, dated 13 November, list under bug fixes:

"codex exec keeps project configuration and MCP servers disabled in untrusted directories, even with --sandbox workspace-write. Use --trust with codex exec or codex review to explicitly save project trust."

Before this release, a repository's configuration and MCP servers could load under codex exec --sandbox workspace-write in a directory you had never marked as trusted. Now they stay off until you opt in with --trust.

OpenAI files this as a bug fix. It names no CVE or advisory, so do not expect a vulnerability scanner to flag older versions.

Also in 0.169.0:

  • "Add or edit custom model providers from the terminal", with device-code sign-in for supported gateways over SSH or without a local browser.
  • Windows sandbox fixes for quoted cmd.exe paths and for PowerShell sessions whose working directory has an unreadable parent.

Why it matters

Two effects, one good and one easy to miss.

The good one. A repository you pulled from someone else can no longer bring its own MCP servers into an exec run just because the sandbox allows workspace writes. Workspace write permission and trust in the repo's config are now separate decisions, which is how they should always have worked.

The easy one to miss. Any pipeline that runs codex exec in a fresh checkout and expects project configuration or MCP servers to load will run without them after the upgrade unless it passes --trust. The release notes describe no warning or error for this, and we have not tested whether one appears, so check the output rather than waiting for a failure.

What changes for you

  • Audit CI first. Find every job that runs codex exec in a fresh checkout and relies on project config or MCP servers.
  • Add --trust selectively. Pass it only for repositories whose configuration you are willing to run.
  • Leave third-party repos alone. Untrusted or external repositories should run without --trust; that is the protection this release adds.
  • Compare outputs after upgrading. The release notes name no warning for skipped config, so a before and after diff of one representative job is the fastest way to catch a change.

What to do

  1. 1 Find CI jobs that run codex exec in fresh checkouts and expect project config or MCP servers.
  2. 2 Add --trust to those commands only for repositories whose configuration you trust.
  3. 3 Leave untrusted third-party repositories without --trust.

Affected tools & models

Never need to catch up again

The weekly delta: only verdict changes and act-now items. No digest filler.

By subscribing you agree to our Privacy Policy. Unsubscribe anytime.