Feature request: semantic overview of Codex threads across projects

Summary

As Codex usage grows, the thread history becomes difficult to navigate. Auto-generated titles are useful at first but can become stale or misleading as a conversation evolves, while a flat global list does not show how related threads contribute to a project.

The underlying problem is not only naming individual chats: users need a compact, trustworthy overview of the work represented by many Codex threads.

Proposal

Add an opt-in semantic index and overview across Codex threads.

Thread titles

• Generate a concise title from the current conversation content.
• Update it only after a meaningful topic or status change, not after every message.
• Allow manual renaming and a "lock title" action to disable further automatic changes.
• Preserve the original title and show when the generated title was last refreshed.

Cross-thread project overview

• Group or cluster threads by project and topic using workspace context plus conversation content.
• Provide both a global view and a project-scoped view.
• For each project/topic cluster, show a compact summary:
• purpose or goal
• current status (active, waiting, blocked, done, or unclear)
• last activity
• important decisions
• next action
• blockers
• related threads and relevant files

PARA-style organization

Optionally suggest PARA-style categories such as Projects, Areas, Resources, and Archive.

These should be suggestions with confidence and a small review queue, not silent filing or file moves. Every derived item should link back to the source thread(s), and users should be able to exclude selected threads or projects.

Control and persistence

• Make the feature opt-in and privacy-conscious.
• Prefer local-first indexing where possible, or clearly show what content is processed remotely.
• Allow rebuilding or refreshing the index.
• Support exporting an overview to Markdown or JSON, or to a user-selected project folder.
• Do not modify the user's filesystem or PARA structure without explicit action.

Expected outcome

A user with many Codex threads should be able to answer quickly:

• What projects are represented in my history?
• Which threads belong together?
• What is active, waiting, blocked, or finished?
• What is the next action?
• Where is the original conversation or relevant file?

This would reduce sidebar clutter while making Codex history useful as a lightweight project-memory layer.

Related issues

• #12564 — allow renaming task/thread titles
• #20115 — archive conversations to a project folder and maintain a project-level conversation index
• #25319 — scope Codex chats to the current workspace/project
• #25084 — improve Codex Desktop history discovery and provide an all-chats/all-projects path

The request here builds on those pieces by adding a semantic, cross-thread overview rather than only renaming or filtering individual threads.