Add “Always allow this file/folder” options to file edit permissions

What variant of Codex are you using?

ChatGPT desktop app on macOS

Powered by Codex & OWL
Version 26.707.61608
Released Jul 13, 2026

What feature would you like to see?

Add scoped persistent edit permissions to the file-edit approval dialog.

When Codex requests permission to edit a file outside the current workspace, the dialog currently offers:

• Allow once
• Allow all edits

I would like two additional options:

• Allow all edits to this file
• Allow all edits in this folder

These permissions should persist for the current session or project, so subsequent edits within the approved scope do not require another prompt.

The dialog should clearly show the file or directory being authorized. For folder permissions, it should also be clear whether the permission includes subdirectories.

Additional information

My concrete use case is temporary files created by Codex under /private/tmp.

Codex created temporary files outside the workspace in /private/tmp and subsequently needed to edit those files. Each edit triggered another permission prompt.

Allow once causes repeated interruptions, while Allow all edits grants substantially more access than necessary.

For example, if Codex creates and works with files in /private/tmp/<specific-directory>/, I would like to authorize edits to that specific directory without granting unrestricted edit permission elsewhere.

Similarly, if only one temporary file needs repeated edits, I would like to authorize that specific file.

This would provide a least-privilege option between approving every individual edit and allowing all edits globally.

Ideally, scoped permissions could also be reviewed and revoked from the app's settings.

I found related requests concerning writable roots and repeated approvals, but this request is specifically for file- and folder-scoped persistent authorization directly from the Codex desktop app's file-edit permission dialog.

Start by reproducing the repeated approval flow in the Codex desktop app and tracing the file-edit permission dialog. Review how the dialog handles “Allow once” and “Allow all edits,” then determine how project or session permissions and the app settings entry for reviewing or revoking them fit together. Done means file- and folder-scoped approvals work with clear boundaries, persist as described, and can be revoked.