Feature Request: Configurable Automatic Conversation Naming Format

[MeezaanD]

What variant of Codex are you using?

App

What feature would you like to see?

Feature Request: Configurable Automatic Conversation Naming Format

Problem

When using Codex heavily across multiple development tasks, the automatically generated conversation titles become difficult to scan in the sidebar.

I often have several conversations in the same project covering code reviews, bug fixes, releases, investigations, and feature work. While Codex generates a description for each conversation, there is currently no way to define a consistent naming convention for those automatically generated titles.

Manually renaming every conversation defeats the purpose of automatic titles.

Requested Feature

Allow users to configure a conversation title template that Codex applies whenever it automatically names a new conversation.

For example, I would configure:

[DD MMM · HH:mm] — <Action>: <Generated Summary>

Codex could then automatically generate:

• [24 Aug · 09:15] — Review: wiCode search changes
• [24 Aug · 10:05] — Fix: wiCode session timeout redirect
• [24 Aug · 11:20] — Release: PR #1481
• [24 Aug · 13:40] — Debug: Redshift integration connection

The <Action> could either be inferred by Codex or selected from configurable categories such as:

Implement, Fix, Debug, Review, Refactor, Release, Plan, Docs, Test, Investigate

Suggested Configuration

Something like:

Conversation title format: [DD MMM · HH:mm] — {action}: {summary}

Possible variables could include:

• {date}
• {time}
• {project}
• {repository}
• {branch}
• {action}
• {summary}

Users could choose whichever variables make sense for their workflow.

Why This Would Be Useful

For developers running many Codex conversations simultaneously, the sidebar effectively becomes a work history.

Consistent automatic naming would make conversations much easier to scan, search, distinguish, and return to without requiring users to manually rename every thread.

The key requirement is that Codex should continue generating the title automatically — users should simply be able to control the format of that generated title.

Additional information

No response

[znbsf]

Disclosure: I maintain codex-task-title-organizer.

This is the exact gap I built it to explore. The plugin applies a structured title shape such as 🟦 Domain｜Project/repository｜Work type｜Concrete object: purpose and re-evaluates the active title only at bounded checkpoints (2, 4, 10). It supports color blocks, semantic icons, or an explicit project-defined marker mapping.

The Hook stores only hashed session/turn identifiers and small counters—not prompt text, generated titles, transcripts, Codex databases, or full paths. That makes it useful as an interim workaround, but a native per-user/per-project format setting would be cleaner and work across surfaces.

Would the team consider either:

• a native Regenerate title / Apply title format action in the task menu; or
• a narrowly scoped official title-generation setting, Hook, or API where users define a shape such as Marker｜Project｜Work type｜Summary, Codex generates the values, and manually edited titles always take precedence?