conversation-history-recorder

To record conversation history, append structured entries to Markdown files stored under /home/gguo/code/history, capturing context, user instructions, feedback, and choices after each turn. This preserves project problems and decisions across conversations without logging code-level details.

The best way to maintain a durable project conversation log is using one Markdown file per project, named after the top-level directory, updating the file with a defined template after each user turn to ensure instructions and choices are preserved exactly.

Conversation history recording for multi-project tasks uses a shared _workspace.md file. The entry records the involved projects within the Context section, ensuring cross-project tasks are documented without forcing a single project file.

No, the conversation history recorder does not log code-level implementation details. It specifically preserves project problems, user instructions, Codex feedback, and user choices across turns to maintain a clean project context.

No, this conversation recorder is specifically scoped to preserve history for projects under /home/gguo/code. Tasks not tied to a single project within this workspace are logged to a general _workspace.md file, but external projects are not supported.