Feature Request: LLM Wiki / Auto-Index Layer for ChatGPT History and Codex Workspaces

What variant of Codex are you using?

App, CLI, Web

What feature would you like to see?

I've been using ChatGPT since 2023. I've had lots of ideas, decisions, project notes, study notes, and technical plans, and many of these get lost in conversation history.

I recently exported my ChatGPT conversation history and started experimenting with re-importing it through Codex into a local Markdown LLM wiki. The goal is to preserve the original chronological chat history while also building an auto-indexed semantic layer around recurring projects, concepts, decisions, open questions, action items, source conversations, and timelines.

The basic workflow is:

1. Export all ChatGPT conversation history.
2. Store the raw export as immutable source material.
3. Use Codex to ingest exported conversation files one file at a time. In my case, these are exported as batches of around 100 conversations per file.
4. Preserve timestamps from the original export, including conversation created time, last updated time, and message-level timestamps when available.
5. Summarize each conversation into source-backed notes.
6. Distill durable ideas into wiki pages for projects, concepts, systems, and timelines.
7. Maintain an index and changelog so the wiki compounds over time.

This works as a DIY process, but it feels like something ChatGPT/Codex could support natively.

The feature request is: add an optional LLM Wiki / auto-index layer on top of chat history and Codex workspaces.

Chronological history should remain the raw timestamped timeline, but users should also be able to browse their knowledge through an LLM wiki.

A major requirement is better timestamp support. Each conversation and wiki-derived entry should preserve:

• Conversation created timestamp — when the chat originally started.
• Conversation last updated timestamp — when the chat was last modified.
• Message-level timestamps — when individual user/assistant messages were sent, when available.
• Source timestamp — when the referenced idea, decision, or note originally occurred.
• Ingested timestamp — when the item was added to the wiki/memory layer.
• Last modified timestamp — when the derived wiki page or memory entry was last updated.

The primary organization could be:

• Projects — long-running efforts that span many chats, files, code sessions, and decisions.
• Concepts — recurring ideas, theories, architectures, patterns, study topics, and research areas.

Then each project or concept page could include structured sections such as:

• Timeline — how the idea or project evolved over time, with source timestamps.
• Decisions — important conclusions, tradeoffs, and architecture choices, linked to when they were made.
• Open Questions — unresolved problems, research directions, and things to revisit.
• Action Items — concrete next steps extracted from conversations.
• Source Conversations — original chats preserved as timestamped evidence behind summaries.
• Related Pages — links to connected projects, concepts, people, files, or code workspaces.

A button like "Update my wiki from this chat" could let the user approve structured updates into project memory or a local Markdown wiki.

This would make ChatGPT/Codex much more useful as a long-term thinking environment, not just a list of previous chats or coding sessions.

Additional information

_No response_