[Feature Request][Windows] Allow configuring a custom file manager for “Open in File Explorer”

What feature would you like to see?

Please add a setting in the Codex Windows app that lets users choose which file manager is used for the project action currently labeled Open in File Explorer.

Ideally this would support either:

• the system default folder handler, or
• a custom executable and arguments, for example:

C:\Program Files\GPSoftware\Directory Opus\dopus.exe
"{path}"

A possible UI could be:

File manager:
- Windows File Explorer
- System default
- Custom

Custom executable:
C:\Program Files\GPSoftware\Directory Opus\dopus.exe

Arguments:
"{path}"

Why this is useful

Some Windows users replace File Explorer with third-party file managers such as Directory Opus. Codex currently appears to use Windows Explorer-specific folder-opening behavior rather than exposing a configurable file-manager target.

This makes the behavior inconsistent for users who have already configured a replacement file manager at the OS/app level.

Current behavior observed with Directory Opus

Directory Opus is configured to replace Explorer for normal folders.

When using Codex's project action:

1. If the project folder is already open in Directory Opus, Codex can bring that existing Directory Opus tab/window to the foreground.
2. If the project folder is not already open in Directory Opus, Codex opens Windows File Explorer instead.

So Explorer replacement only works partially in this workflow.

Expected behavior

Codex should provide an explicit way to choose the file manager used for opening project folders.

At minimum, a System default option would help. A Custom executable + arguments option would make the behavior reliable for Directory Opus, Total Commander, OneCommander, Files, and similar tools.

Platform

• Codex Desktop
• Windows

Notes

This is different from the existing setting for the default app/open location. The request is specifically about the project/folder action currently exposed as Open in File Explorer.

Start by locating the Windows Codex Desktop entry point for the project action labeled “Open in File Explorer” and the existing default-app/open-location setting. Trace how the project path is passed to the current folder-opening behavior. Done means users can choose Windows File Explorer, the system default, or a custom executable with arguments, and the project action uses that choice.