Symlinks are not resolved for permission checks
Open 💬 3 comments Opened Mar 19, 2026 by fingon
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.115.0
What subscription do you have?
plus
Which model were you using?
_No response_
What platform is your computer?
Darwin 25.3.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
WezTerm
What issue are you seeing?
Symlinks are not resolved for project directories (always)? I started it at (shell) path ~/projects/x, while it is really ~/share/1/projects/x, and I got permission prompt to edit every file which is infuriating.
What steps can reproduce the bug?
Uploaded thread: 019d0524-0585-7d40-83ae-f525cce8c65c
What is the expected behavior?
Resolve symlinks to figure where the repository really leads to for all permission checks.
Additional information
_No response_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Which directory did you add to the workspace to give write access? Try adding both the resolved path and the non-resolved path (ideally codex ought to give access to both). I've fixed this with a couple of commits 7515881f0 and c010a91c1 which worked for me.
It was fresh project and I just invoked codex from its git root. I think it might have been initial run specific problem as in subsequent runs I do not think it surfaced again ( despite using symlinked paths a lot to start it ). I am not sure why it did not happen in other ones though.