# Codex exec keeps project config and MCP servers off in untrusted directories

> Codex CLI 0.169.0 requires explicit project trust for codex exec, so project configuration and MCP servers stay disabled in untrusted directories.

- Status: official (From the company, authors or authority themselves, with a link to their own page.)
- Topic: Products
- Published: 2026-11-13T08:39:10+00:00
- Updated: 2026-11-13T09:08:53.434378+00:00
- Web page: https://ai-news.ikangai.com/story/codex-exec-keeps-project-config-and-mcp-servers-off-in-untrusted-directories/
- Seen in: Codex CLI releases
- Change: breaking_change (Breaking change)
- Applies to: Codex CLI 0.169.0, codex exec, codex review, --sandbox workspace-write, MCP servers

## What changed

Codex exec keeps project configuration and MCP servers disabled in untrusted directories, even with --sandbox workspace-write, and they load only after trust is granted with --trust.

Codex CLI 0.169.0 changes how the non-interactive codex exec command treats project directories it has not been told to trust. In those directories, project configuration and MCP servers stay disabled, even when the run uses --sandbox workspace-write. To turn them on, a user passes --trust to codex exec or codex review, which saves the project trust. The release notes list this under Bug Fixes. The changelog entry, #60041, is titled "Require explicit project trust in non-interactive runs."

The distinction being enforced is between the sandbox and trust. According to the release notes, the workspace-write sandbox does not decide whether a project's own configuration loads. Those settings stay disabled in untrusted directories even with that sandbox mode. Trust is a separate requirement. For codex exec, a project must be explicitly trusted with --trust, which saves the project trust.

The fix is one of several changes in the same release that touch how Codex handles MCP servers. The terminal no longer stays busy waiting for MCP servers that a shared app server did not report. The release also adds opt-in lazy startup for cached stdio MCP servers.

## Why it matters

Scripts and automated pipelines that run codex exec may now behave differently in directories that have not been trusted, so project-level MCP tools and settings will not load until trust is granted.

## What you can do

Teams running codex exec in CI or scripts should check whether their jobs rely on project config or MCP servers and add --trust where that is intended.

## Original source

- [Release 0.169.0 · openai/codex · GitHub](https://github.com/openai/codex/releases/tag/rust-v0.169.0)

---

AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it.

Cite as: IKANGAI AI News, "Codex exec keeps project config and MCP servers off in untrusted directories", 2026-11-13, https://ai-news.ikangai.com/story/codex-exec-keeps-project-config-and-mcp-servers-off-in-untrusted-directories/
