Skip to content

"sed" command fails when the file path has round brackets in it #2458

@liarco

Description

@liarco

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:

Image

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtool-callsIssues related to tool calling

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions