YOLO mode still prompts for local commands due to temporary IPC sockets

Summary

When I run Codex CLI in YOLO mode, I still get interactive approval prompts for local-only commands. The prompts interrupt the terminal session even though the commands do not require network access or elevated host access.

Example

Codex first reports Permissions updated to Full Access, then asks me to approve:

npm run pipeline:docs:refresh

The reason given is that the local TypeScript tool uses a temporary local IPC socket. After approving and allowlisting that exact command prefix, Codex runs it successfully, but it prompts again for the next local command:

npm run pipeline:docs:check

with the same temporary-local-IPC-socket rationale.

Expected behavior

If the CLI was started with --dangerously-bypass-approvals-and-sandbox (or an equivalently configured YOLO mode), no interactive command approvals should appear. A temporary local IPC socket should not re-enable the approval flow.

If the current behavior is intentional, the UI should clearly distinguish “Full Access” from the stricter bypass-all-approvals mode and explain why the configured mode was not applied.

Environment

• Codex CLI: 0.144.4
• OS: Linux/WSL environment
• Command examples: repository-local npm run pipeline:docs:refresh and npm run pipeline:docs:check

Impact

This breaks unattended/YOLO workflows: the CLI pauses for each new command prefix despite the session being expected to run without confirmations.