Feature request: archive Codex conversations to a project folder

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

1. 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.