PuppyIP Resource Center
AI Tool Tutorials 6 min read Published 2026-11-14

Codex CLI 0.169: Project Trust and Approved-Plan Handoffs

Codex CLI 0.169 separates workspace write access from project trust. Approved plans are checked in the fresh session before the UI clears and switches context.

Codex CLI codex exec Project configuration and trust Approved plans

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • In an untrusted directory, codex exec keeps project configuration and MCP disabled even with --sandbox workspace-write; permission to write files does not establish project trust.
  • codex exec and codex review can use --trust to save project authorization for current and future sessions. The grant persists even with --ephemeral.
  • Trust can load project MCP configuration and permit its commands to run outside the sandbox. Review the project configuration before an authorized operator grants trust.
  • An approved plan is first attached and checked by the fresh executor. If attachment access fails, the client tries the complete plan; if it cannot fit, the operation errors and keeps the current session.

workspace-write grants file access, not project trust

Codex CLI 0.169.0 was released on November 13, 2026. Its release notes say that codex exec keeps project configuration and MCP servers disabled in untrusted directories, even when run with --sandbox workspace-write. That sandbox setting controls what the task may write in the workspace; it does not confirm that project configuration or MCP commands are safe to load.

When automation can edit files but cannot see expected project settings or MCP tools, keep these boundaries separate: sandbox permissions govern allowed operations, while project trust governs whether project configuration and its MCP setup load. The ability to write in a workspace is not evidence that the project has been reviewed.

--trust saves project authorization for exec and review

Version 0.169 adds --trust to codex exec and codex review so an operator can explicitly save trust for a project. The grant applies to the current and future sessions. Adding --ephemeral does not make this project trust one-time; do not assume that an ephemeral run will revoke it.

This choice allows project configuration and MCP to participate in execution, and MCP commands may run outside the sandbox. The CLI refuses to trust a project that is explicitly marked untrusted, and --trust cannot be combined with --ignore-user-config.

Review the configuration before an authorized trust decision

Before using --trust, confirm that the working directory is the intended project and read the project configuration, MCP server definitions and startup commands that will be loaded. Check what those settings launch, what resources they can reach and whether that access fits the task’s authorization. The file-write sandbox does not replace this review.

If the directory’s origin, configuration or command purpose is unclear, keep running it as untrusted until you understand it. Use --trust only when the review supports the decision and the operator is authorized to make it. The release does not ask users to bypass warnings or grant trust automatically.

Verify the approved plan before clearing the old context

“Yes, clear context and implement” now saves the approved plan as an app-server attachment and sends the fresh session a short prompt that refers to it. During preparation, the new thread’s executor verifies that it can read the attachment and that the contents match the approved plan. This checks both access and content; merely creating a file is not enough.

If the attachment cannot be written or read, the client tries to include the complete plan as proposed_plan tool output in the new session’s context, subject to context and truncation limits. Handoff can continue only when the whole plan fits; a truncated plan is not treated as a complete handoff.

A failed preparation keeps the session; other fixes stay scoped

If the complete plan cannot fit within the limits, the flow reports an error and keeps the current session. The UI clears context and switches threads only after plan preparation succeeds. This lets the user handle the failure in the original session without losing a plan that was never handed off. This describes the 0.169 client flow; it is not a report of a local CLI upgrade or configuration test.

The same release also lists bounded fixes for Windows sandbox handling of quoted cmd.exe paths and PowerShell working directories with unreadable parents; terminal waits for MCP servers that a shared app server did not report; and interrupted turns, delayed aborts or file-approval cancellations affecting a later turn. These are the fixes named in the release, not evidence that every busy or long interruption has the same cause or that every interruption is resolved.

Sources

Frequently Asked Questions

Does --trust switch providers or grant model, quota or regional access?

The flag does not itself grant account-level model eligibility, quota or regional access; the 0.169 changes describe project-configuration and MCP trust. Loading project configuration may affect project-level settings, so review the effective configuration and verify account and provider access separately.

Does a CLI release prove the desktop, editor or remote host is also updated?

No. The release notes describe Codex CLI. Check the version on the host, executor and client that actually run the command. This article did not install or upgrade the CLI, change settings or grant project trust.