Project-Specific Conversation Histories

What feature would you like to see?

Problem:
Currently, when I use the Codex CLI command codex resume, it displays all conversations I have had with Codex, regardless of which project or working directory I am in. This makes it difficult to manage and review discussions that are specific to separate projects.

Request:
I would like Codex CLI to implement a mechanism for storing conversation history on a per-project basis. When I use codex resume in Project A's directory, it should only show conversations that occurred within Project A. Similarly, in Project B, Codex CLI should only display conversations from Project B. This would greatly improve contextual relevance and productivity for users managing multiple projects.

Proposed Solution:

• Store conversation histories in a way that associates them with their respective working directories or unique project identifiers.
• Update the behavior of codex resume so it only retrieves conversations related to the current directory/project.
• Optionally, provide a way to merge or migrate histories if a project is reorganized or moved.

Benefits:

• Easier to track project-specific conversations
• Enhanced productivity by reducing clutter
• Better organization for users working on multiple projects

Thank you for considering this feature!

Additional information

_No response_