codex - 💡(How to fix) Fix Project-scoped chat history in the Codex IDE extension [1 comments, 2 participants]

TL;DR

Implement a project-specific chat history feature in the Codex IDE extension to improve organization and context.

Guidance

• To achieve project-specific chat history, consider adding a unique project identifier to each conversation and filtering the history view based on the current project.
• Introduce a setting to allow users to choose between global and per-project history views, ensuring flexibility and user preference.
• When implementing the feature, ensure that the conversation data is properly scoped and isolated to prevent cross-project information leaks.
• Consider the storage and retrieval mechanisms for conversation history to ensure efficient data management and minimal performance impact.

Example

No code snippet is provided due to the lack of technical implementation details in the issue.

Notes

The implementation details of the project-specific chat history feature are not specified, and the exact technical approach may vary depending on the existing architecture and technology stack of the Codex IDE extension.

Recommendation

Apply a workaround by introducing a manual project-specific notation or tagging system for conversations until a native project-specific chat history feature is implemented, allowing users to somewhat organize their conversations by project.