Add chat export support using existing Codex logs
Resolved 💬 5 comments Opened Oct 26, 2025 by kgruiz Closed Nov 11, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What feature would you like to see?
Codex CLI already saves full chat logs in ~/.codex, but they’re stored as verbose JSON with a lot of internal data.
This proposal is to make those chats exportable in a readable format (Markdown or plain text) that includes only user and model messages.
---
Why is this useful?
- Lets users export a finished chat and continue it in another session, keeping context across resets.
- Complements issue #5348 (Session Chaining) — not the preferred long-term solution, but a practical interim step that supports the manual workaround discussed in its comments.
- Uses existing saved data, requiring only a simple export layer.
- Improves usability and reproducibility for long-running projects.
Additional information
This would be a low-risk enhancement that only exposes readable exports of logs Codex already stores locally.
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks for the suggestion. I think this may be a duplicate of https://github.com/openai/codex/issues/4232. If so, let's close this one and consolidate any details into the previous one.
Closing in favor of #2880
For anyone landing here, I built harness-recall (https://github.com/timothydillan/harness-recall), which tackles this across multiple tools in one CLI. It reads sessions from Codex, Claude Code, and Cursor, indexes them, and exports to Markdown, HTML, or JSON (your choice).
A few things beyond what's been shared in this thread:
Install using: pip install harness-recall
Hope it helps!
Hey, I have built a tool for exporting entire codex session logs / conversations, with options: https://github.com/ezyyeah/codex-export