"sed" command fails when the file path has round brackets in it
Resolved 💬 5 comments Opened Aug 19, 2025 by liarco Closed Jan 17, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.22.0
Which model were you using?
gpt-5-mini
What platform is your computer?
_No response_
What steps can reproduce the bug?
I'm running Codex in a NextJS project where some folders use brackets in their names in order to support some organizing features and dynamic paths.
Here is what I get when Codex need to access a file in one of those folders using sed:
<img width="636" height="106" alt="Image" src="https://github.com/user-attachments/assets/5ffaed87-3cd5-4447-8338-34cdd3c8bd4d" />
I expect this to happen with other special characters too, but I didn't catch it yet.
What is the expected behavior?
It should be able to use the correct syntax no matter the path.
What do you see instead?
The command fails.
Additional information
_No response_
5 Comments
Same here, any idea how to avoid it failing?
This is a huge problem when workign with Next.js projects
Closing out old bugs.
why is this an old bug when this is still happening in my latest codex?
@farshid-campfire, if you're seeing a similar behavior with the latest version, please open a new bug report and fill out all of the information in the template. Also use
/feedbackto upload your logs and session details and include the thread ID in the report.