[Codex App][Windows] Make response file references and artifact cards draggable to external apps

What variant of Codex are you using?

Codex App / Desktop app

Platform

Windows 11

What feature would you like to see?

I would like file references and artifact cards shown in Codex responses to be draggable outside the Codex app as real OS file objects.

Example: when Codex creates a file and shows a response link/card like:

generated_report.csv (line 1)

I want to be able to drag that link/card directly into another application, such as a browser upload field, Windows Explorer, VS Code, an editor, or another desktop app.

Current behavior

The file reference is visible and clickable inside Codex, but it does not behave like a real draggable file. To use the file elsewhere, I need to open or reveal the containing folder first, then drag the file from Windows Explorer. This interrupts the workflow.

Desired behavior

Codex response file references and file cards should support drag-out behavior:

• dragging the file card should provide the actual local file as the drag payload
• dragging the blue filename link should also drag the referenced file, not just text
• on Windows, this should use normal filesystem drag behavior so other apps receive the file as if it came from Explorer
• if the reference includes a line number, the drag should still transfer the file; the line reference can be preserved as text/metadata if supported

Why this matters

Codex often creates CSVs, patches, logs, screenshots, reports, and other artifacts. After Codex produces a file, the natural next step is often to drag it into another app. Making response file references draggable would remove the extra “open folder first” step and make Codex-generated files feel like real local artifacts.

Suggested labels: app, enhancement, windows-os.

Related issues:

• #19785 — draggable workspace file tree/sidebar
• #17136 — improve file reference interactions
• #17591 — Windows desktop app file links / real filesystem paths