Allow Unix-style forward slashes (/) for @ file mentions on Windows
What version of the Codex App are you using (From “About Codex” dialog)?
26.415.208188
What subscription do you have?
Basic
What platform is your computer?
_No response_
What issue are you seeing?
When trying to reference a file inside a directory using the @ mention feature on Windows, the search filter fails if you use a Unix-style forward slash (/). For example, typing @openapi-clients/Dockerfile results in "No results".
However, if you use a Windows-style backslash (\), such as @openapi-clients\Dockerfile, the file suggestions appear correctly.
The main inconsistency here is that the autocomplete dropdown UI actually displays the paths using Unix-style forward slashes (e.g., showing .gitignore openapi-clients/forms). Because the UI displays a /, users naturally type a / to continue filtering, which breaks the search.
Folder:
<img width="1540" height="593" alt="Image" src="https://github.com/user-attachments/assets/2c065df4-407a-44ab-bf14-34707b9be546" />
Unix-style forward slash (/):
<img width="1586" height="263" alt="Image" src="https://github.com/user-attachments/assets/4d4596a9-b68b-4a3a-b846-bacbecc4a80a" />
Windows-style backslash (\):
<img width="1513" height="375" alt="Image" src="https://github.com/user-attachments/assets/ae616eb1-5b6d-45a0-8c4e-2b94ee675e44" />
What steps can reproduce the bug?
- Open the Codex App on a Windows machine.
- In the chat input, type
@followed by a known directory name (e.g.,@openapi-clients). - Notice that the file suggestion dropdown displays subdirectories with forward slashes (e.g.,
openapi-clients/forms). - Continue typing to filter for a specific file using a forward slash:
@openapi-clients/Dockerfile. - Observe the dropdown says "No results".
- Replace the forward slash with a backslash:
@openapi-clients\Dockerfile. - Observe that the correct file suggestions now successfully appear.
What is the expected behavior?
The @ file mention search should accept Unix-style forward slashes (/) as path separators on Windows. At the very least, the required input format should match the display format shown in the UI's suggestion list to prevent user confusion. Ideally, it should gracefully handle both / and \ on Windows.
Additional information
_No response_