Codex App crashes when Open in File Explorer targets unavailable removable drive

Codex App bug report: "Open in File Explorer" crashes when attachment path is unavailable

Summary

In the Codex desktop app on Windows, selecting Open in File Explorer from an attachment menu can crash the entire Codex app when the attachment points to a file on a removable drive that is currently unavailable.

The app should show a non-fatal error such as "Path does not exist" or "Drive is unavailable" instead of terminating.

Environment

• Product: Codex desktop app
• OS: Windows 11 Home, Chinese edition
• OS version: 10.0.26200, 64-bit
• Thread URL: codex://threads/019eea77-e6d4-76e1-8bc4-8e3497a7395f
• Affected action: attachment menu -> Open in File Explorer

Affected file path

The attachment pointed to a PPTX file on a removable USB drive using drive letter F:.

Example pattern:

F:\...\20260614\Al_MoOx_interface_2groups_template_v2.pptx

The original path contained non-ASCII Chinese folder/file names, but the core trigger appears to be that the F: drive was unavailable when the menu item was clicked.

Steps to reproduce

1. In Codex desktop app on Windows, create or view a thread with a file attachment whose local path is on a removable drive, for example F:\...\file.pptx.
2. Close Codex or leave the thread.
3. Unplug or otherwise unmount the removable drive so the original drive letter no longer exists.
4. Reopen the thread.
5. Open the attachment menu.
6. Click Open in File Explorer.

Actual behavior

Codex desktop app crashes/exits.

Expected behavior

Codex should not crash. It should handle the missing path gracefully and show an inline/toast/dialog error, for example:

Cannot open file location: path does not exist or drive is unavailable.

Confirmation

After reconnecting the USB drive and restoring the F: drive, the same attachment could be opened from the same Codex thread. This suggests the file and thread data were valid, and the crash was triggered by missing-path handling.

Privacy note

This report intentionally does not include the PPT file or full session logs, because logs and documents may contain private research data.