Separate Codex's File Access From Its Network Access
A task may need to edit a local script while having no reason to contact a production service. Treat those permissions as separate decisions.
Before automating with Codex, inspect the effective sandbox and approval settings for the environment you are using. Test the required file operation in a disposable workspace and document any network dependency explicitly. A sentence in the prompt does not replace an enforced boundary.
If a validation command reaches a live database, replace that test input with a local fixture or a deliberately configured test service. Keep the same assertion about the output. The useful question is not whether the task has broad permission, but whether it has the access needed to complete a checkable job without unintended external effects.
