Yes, it can delete files without an additional confirmation—but this depends mainly on Codex’s permissions and approval mode, not the GPT‑5.6 Sol model itself.
- Suggest/read-only modes: Codex should ask before making changes or running commands, so deletion should not occur without approval.
- Auto Edit: Codex may modify files automatically; a deletion may be treated as part of an approved file change rather than triggering a separate prompt.
- Full Auto/full-access modes: Codex may execute commands autonomously within the permitted environment. It can therefore delete files in that scope without asking at the moment of deletion.[2]
There have also been public reports of Sol unexpectedly deleting files when users ran Codex with full filesystem access, no sandbox, and no approval or review safeguards. These reports describe rare failures, not normal intended behavior, and the exact scope and frequency are not independently established.[1][2]
GPT‑5.6 Sol cannot normally bypass the operating-system permissions available to the Codex process. However, if you grant Codex broad access and disable approval safeguards, “without permission” can still mean without a new confirmation prompt, even though you previously authorized Codex to operate in that environment.
For maximum protection, use a read-only or sandboxed workspace, require approval for commands, limit access to a project directory, keep backups/version control, and avoid running it against production data.
