Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Feature request: archive Codex conversations to a project folder [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20115•Fetched 2026-04-29 06:22:49
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
birdflybirdfly
Participants
birdflybirdfly
Timeline (top)
labeled ×3

Please add a way to archive or associate a Codex conversation with a specific local project folder/workspace, and export the full conversation history as a project artifact.

Root Cause

This would make Codex more useful for professional long-running projects where the conversation is part of the working record, not just a transient chat. It is especially useful for code reviews, legal/document review workflows, research projects, and multi-stage implementation plans.

RAW_BUFFERClick to expand / collapse

Summary

Please add a way to archive or associate a Codex conversation with a specific local project folder/workspace, and export the full conversation history as a project artifact.

Problem

For long-running work, the conversation itself becomes part of the project record: decisions, review notes, rationale, follow-up tasks, and references to generated files often live in the thread. Today, users can create a manual summary file, but the Codex conversation remains separate from the project folder and cannot be moved, indexed, or exported as a first-class project artifact.

This makes it harder to:

  • hand off work to another person,
  • audit why certain changes were made,
  • resume a project weeks later,
  • keep multiple project conversations organized,
  • preserve a complete record of the discussion alongside the files it produced.

Requested functionality

It would be useful if Codex supported one or more of the following:

  1. Assign or move a conversation to a local project folder/workspace.
  2. Export a full conversation to Markdown, JSON, or PDF from the app.
  3. Generate and maintain a project-level conversation index, for example .codex/conversations/ or similar.
  4. Allow project-scoped search across prior Codex conversations.
  5. Include links from exported conversations to files created or edited during the thread.

Expected user experience

Example flow:

  1. User opens a Codex conversation used for a project.
  2. User selects Archive to project... or Export conversation....
  3. Codex lets the user pick the workspace/project folder.
  4. Codex writes a durable artifact such as:
    • .codex/conversations/<date>-<title>.md
    • .codex/conversations/index.json
  5. The project can later be reopened with the conversation history discoverable from that project context.

Why this matters

This would make Codex more useful for professional long-running projects where the conversation is part of the working record, not just a transient chat. It is especially useful for code reviews, legal/document review workflows, research projects, and multi-stage implementation plans.

Privacy / control considerations

The feature should be user-initiated and local-first. Users should choose exactly which conversation is exported and where it is saved.

extent analysis

TL;DR

To address the issue, consider implementing a feature to export Codex conversations to a local project folder, allowing users to archive and associate conversations with specific projects.

Guidance

  • Implement a "Archive to project" or "Export conversation" feature that enables users to select a workspace/project folder and export the conversation history as a durable artifact, such as a Markdown or JSON file.
  • Design a project-level conversation index, like .codex/conversations/, to store exported conversations and facilitate discovery.
  • Ensure the feature is user-initiated and local-first, allowing users to choose which conversations to export and where to save them.
  • Consider adding links from exported conversations to files created or edited during the thread to enhance the user experience.

Example

# Example exported conversation file
## Conversation Title
### Date: 2023-02-20
- Discussion point 1
- Discussion point 2
[Link to generated file](path/to/file)

Notes

The implementation should prioritize user control and privacy, ensuring that conversation exports are intentional and locally stored.

Recommendation

Apply a workaround by manually creating a summary file and storing it in the project folder until a native export feature is implemented, as this provides a temporary solution for preserving conversation history alongside project files.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#conversation history#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Feature request: archive Codex conversations to a project folder [1 participants]