In Home directory Sandbox is set to 'workspace-write' instead of 'read-only'

Open 💬 4 comments Opened Feb 2, 2026 by kingtistel

What version of Codex is running?

codex-cli 0.93.0

What subscription do you have?

Business

Which model were you using?

gpt-5.2-codex

What platform is your computer?

Darwin 25.2.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

iTerm2

What issue are you seeing?

When starting codex-cli in the Home directory -- or any directory not under version control -- after the first time, codex is started with Sandbox: workspace-write and Approval: untrusted instead of read-only / on-request.

<img width="632" height="500" alt="Image" src="https://github.com/user-attachments/assets/fbc31c34-221d-44e3-b744-1dd749fa2e65" />

What steps can reproduce the bug?

  1. Start codex in Home directory -- or any directory not under version control -- for the first time,
  2. You're presented with a question to select the approval policy -- defaulted to require approval,

<img width="859" height="116" alt="Image" src="https://github.com/user-attachments/assets/aa13483b-4ed3-4868-8624-7f845cd1e11d" />

  1. Accept the default,
  2. Check status with /status -- it shows Sandbox: read-only and Approval: on-request,
  3. Exit and relaunch codex
  4. Check status with /status -- it now shows Sandbox: workspace-write and Approval: untrusted.

What is the expected behavior?

Expected is that each time starting codex from Home directory or any directory not under version control:

  1. Be asked our approval selection,

-OR-

  1. Start with the previously selected choice.

(¿ How would we change our selection in this flow is chosen ?)

Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗