Quick Chat does not render generated files as downloadable attachments
What version of the Codex App are you using?
Codex Desktop 26.721.81911 (5973)
What platform is your computer?
macOS 15.7.8, Apple Silicon (arm64)
What issue are you seeing?
When the assistant creates a file in Codex Quick Chat, the response displays the file reference as ordinary text instead of a clickable/downloadable attachment.
For example, after asking Quick Chat to create test.txt containing hello, the response shows text such as 下载 test.txt, but there is no attachment card or working download link.
The same cloud conversation opened in ChatGPT Web renders the generated file as a downloadable attachment. This indicates that file generation and backend storage succeeded, but Quick Chat does not render the generated-file attachment metadata/UI.
What steps can reproduce the bug?
- Open Codex Quick Chat.
- Ask:
Create test.txt with the content hello. - Wait for the assistant response.
- Observe that the response only shows a textual file reference; it cannot be clicked or downloaded.
- Open the same conversation in ChatGPT Web.
- Observe that the generated file is rendered there as a downloadable attachment.
What is the expected behavior?
Quick Chat should render generated files as first-class downloadable attachments, consistent with ChatGPT Web, including at least a clickable filename or download action.
What is the actual behavior?
Quick Chat renders only plain text for the generated file, so the user cannot retrieve it from the Quick Chat UI.
Additional information
This is distinct from local workspace file-link handling: the file is generated as a cloud-chat attachment and is downloadable from the same conversation on ChatGPT Web. The issue appears limited to attachment rendering in Codex Quick Chat.
1 Comment
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action