Persisting approvals for file edits does not work

Resolved 💬 4 comments Opened Apr 13, 2026 by tonimelisma Closed Apr 21, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.120.0

What subscription do you have?

The most expensive one

Which model were you using?

gpt-5.4 xhigh

What platform is your computer?

Linux 6.17.0-14-generic x86_64 unknown

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

When editing files, I get a permission prompt for each edit even when choosing "yes, and don't ask for this file ever again".

What steps can reproduce the bug?

Uploaded thread: 019d85a5-580d-7751-9225-31275745fff5

What is the expected behavior?

When I choose "don't ask for permission to edit this file", it would not ask permission to edit that file again.

Additional information

The broken permission handling system is making codex unusable for me and I've gone and cancelled my $200/month subscription. Please try adopting Claude Code's permission system (e.g. authorize all edits within directory codex is running, have simple hooks for scripts I can use to auto-approve chosen commands) as is, they've really figured this out. The only reasonable option for codex seems to be to run it with full permissions and that's not feasible for my use cases.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #17028
  • #17623
  • #16911

Powered by Codex Action

bkoropoff · 4 months ago

This is a recent regression in behavior. I think it used to be possible to accept file edits for the session. Now you can only do it on a per-file basis, but it doesn't actually remember the choice. This makes codex completely unusable; I don't understand how this change ever shipped in a paid product.

viyatb-oai contributor · 4 months ago

Please try the latest release version 0.122.0 and let me know if you are still facing this!

nikhil-marathe-skydio · 3 months ago

I'm seeing this same issue on v0.130.0 as well.
This is on Linux, in a trusted workspace.