Codex codex --sandbox danger-full-access --ask-for-approval never with resume not fully

Resolved 💬 2 comments Opened Oct 18, 2025 by GhouI Closed Jan 10, 2026

What version of Codex is running?

v0.47.0

What subscription do you have?

plus

Which model were you using?

gpt5-high

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

When running with Codex, I normally use the command codex --sandbox danger-full-access --ask-for-approval to ensure that I never skip any command prompts. However, when we end the conversation and then resume it, I am still asked for permissions. It should be able to save the state from the previous conversation if I used the sandbox danger option, and I should be able to change it by using codex resume

What steps can reproduce the bug?

Run Codex without needing sandbox full access permissions.
Exit and save the Codex session.
Resume the Codex conversation, but you still require permissions even though they were granted in previous conversations.

What is the expected behavior?

Saving the state of sandbox behaviour per conversation

Additional information

_No response_

View original on GitHub ↗

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