Allow deleting irrelevant threads from a project

Problem

Currently, Codex only allows archiving threads, but not deleting them.

In real-world usage, users often accidentally create threads that are unrelated to the current project, for example:

• Asking a question in the wrong project window
• Testing prompts or model behavior
• Sending an accidental message
• Starting a conversation that has no engineering value
• General discussions unrelated to the project

These threads may not involve any file modifications, command executions, or agent actions, yet they remain permanently attached to the project history.

As the number of threads grows, project history becomes cluttered and harder to navigate.

Proposal

Allow users to permanently delete threads that have no engineering impact.

Possible criteria could include:

• No files were modified
• No commands were executed
• No agent tasks were created
• The thread contains only a small number of messages

Threads that involve actual engineering activities (file changes, command execution, agent workflows, etc.) can continue to use the existing Archive mechanism to preserve auditability.

Why this matters

Codex treats conversations as part of the development workflow, which makes sense for engineering tasks.

However, not every thread is an engineering artifact. Users should have a way to remove accidental or irrelevant conversations that do not contribute to the project.

This would:

• Keep project history clean
• Reduce friction caused by mistakes
• Preserve audit requirements for meaningful work
• Improve the experience for individual developers and small teams

Thank you for considering this feature.