“Copy path” uses forward slashes on Windows, producing an invalid Windows path

Open 💬 1 comment Opened Jun 28, 2026 by ZenulAbidin

What version of the Codex App are you using (From “About Codex” dialog)?

26.623.42026

What subscription do you have?

Pro 20x

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When Codex emits a filename/path that is copyable, right-clicking it and selecting Copy path copies the path using forward slashes / instead of Windows backslashes \.

This makes the copied path invalid or inconvenient to use in standard Windows contexts such as Explorer, Command Prompt, PowerShell commands expecting a native path, or other Windows applications.

Example

If Codex shows a file path like:

C:\Users\User\project\src\main.py

Using Copy path may copy something like:

C:/Users/User/project/src/main.py

What steps can reproduce the bug?

On Windows, Copy path should copy a native Windows path using backslashes:

C:\Users\User\project\src\main.py

What is the expected behavior?

The copied path uses forward slashes:

C:/Users/User/project/src/main.py

Action used: right-click copyable filename/path → Copy path

Additional information

Why this matters

The feature is specifically labeled Copy path, so on Windows it should produce a Windows-native path. Forward-slash paths may work in some developer tools, but they are not the expected format for Windows paths and can fail or require manual correction in common Windows workflows.

Suggested fix

When running on Windows, normalize paths copied via Copy path to use backslashes \, or provide separate options such as:

  • Copy path
  • Copy WSL path (with /mnt/c/ prefix)
  • Copy Windows path

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗