Unverified50% confidenceFactExact time
On Codex CLI 0.162.1, even if the config sets `approval_policy = "on-request"`, non-interactive runs (`codex exec`) still show `approval: never`, because there is no one to ask in non-interactive scenarios.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedCODEX_CLI_NO_DAEMON=1 is a process-level configuration that is passed to all child processes along with the shell session or container environment; whereas the --disable-daemon CLI argument only takes effect for the current command.65% similarUnverifiedCodex CLI runs in approval mode by default, pausing to wait for manual confirmation each time it writes a file or runs a command.64% similarUnverifiedOnly Claude Code sessions started with the clappa command are protected by OpenAPPA; running claude directly does not enable OpenAPPA and does not prompt the user.62% similarUnverifiedCodex's `codex exec` is a non-interactive run mode; unlike the interactive TUI, it runs in a read-only sandbox by default and the agent cannot write files; to let it modify code and trigger tests, you must explicitly pass `--sandbox workspace-write`.60% similarUnverifiedClaude Code's no-prompt mode allows reads that originally require no approval and already-authorized tools to proceed, but directly rejects any action that would normally trigger a confirmation dialog60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1066308API
curl https://kongchang.com/api/v1/knowledge/claims/1066308MCP
get_claim(id=1066308)