Add local conversation export instead of only Copy as Markdown
Codex app version
Desktop Codex: 26.602.40724 — released Jun 5, 2026
Platform
- macOS Tahoe
26.5.1 - Apple Silicon MacBook Pro
- Pro plan
Summary
Please add a built-in feature to export a Codex conversation to a local document/file, instead of only providing Copy as Markdown.
Currently, Codex provides a Copy as Markdown option for a conversation. This is useful for short conversations, but it is not enough for very long sessions.
Why export is needed
For long Codex conversations, exporting directly to a local file is often more useful and more reliable than copying Markdown to the clipboard.
In my current workflow, if I use Copy as Markdown on a very long conversation and then paste it into Microsoft Word, Word can become unstable or crash. This makes it difficult to archive, review, share, or preserve long Codex task histories.
A direct export feature would avoid relying on the clipboard and would be much safer for long-context sessions.
Expected behavior
Codex should provide an option such as:
Export conversation...
Save conversation as...
Export as Markdown
Export as PDF
Export as HTML
Export as DOCX
At minimum, exporting to a local .md file would already be a major improvement over clipboard-only copying. Additional export formats such as PDF, HTML, or DOCX would be even more useful.
Current behavior
The conversation menu provides Copy as Markdown, but there is no direct local export option.
For very long conversations, copying Markdown and pasting it into another app can be unreliable and can crash the receiving app.
Why this matters
Codex conversations often contain important development history, debugging context, implementation decisions, test results, file changes, and task progress. Users may need to keep these records locally for review, documentation, handoff, or future reference.
For long sessions, direct export is a much more robust workflow than copying everything to the clipboard and pasting into another editor.
Request
Please add a local conversation export feature to Codex Desktop. The export should preserve the conversation content in a structured file and avoid requiring users to copy huge Markdown content through the clipboard.
2 Comments
+1
Let users backup/restore the chat context exactly
Disclosure: I maintain an unofficial local workaround for this use case:
https://github.com/Ann-Diana/codex-project-chat-exporter
It does not add a native “Export conversation” button to the Codex app, but it reads the local Codex session files directly and exports them without using the clipboard.
It can bulk-export active and archived sessions into:
The exporter runs locally, makes no network requests, and supports Windows, macOS, and Linux through Node.js. A Windows launcher is included.
Current limitations: it only works for sessions that exist locally, does not export directly to PDF or DOCX, and does not restore conversations into the Codex UI.
Posting this in case it is useful as an interim archival workaround while a native local export feature is not available.