Add tab titles for chats based on conversation

Resolved 💬 9 comments Opened Jan 25, 2026 by BaldrianSector Closed Mar 26, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What feature would you like to see?

Add dynamic titles to Codex CLI conversations used for tabs and resume

I use multiple instances of Codex at the same time, but find it hard to keep track of which conversations contain what. It would be a big quality of life improvement if each tab was named based on what was going on in the conversation, just like ChatGPT labels each chat session.

This could also be used for summarizing and identifying each conversation when using codex resume.

Additional information

Minimal solution would be to set the title based on first message or first meaningful user message, but could be improved with automatic retitling and manual trigger of tilte update.

View original on GitHub ↗

9 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #8430

Powered by Codex Action

BaldrianSector · 5 months ago

I believe my feature request is slightly different from #8430 & #4163.

My suggestion is also to have titles, but have them auto generated based on the chats. I need this for tab management, rather than just for resume as the other two issues request. I see tab titles as a general encouragement of running multiple sessions at once, where resume titles are focused on organizing and finding previous conversations.

swordfish444 contributor · 5 months ago

@etraut-openai This feels closely related to (but slightly broader than) #8430 / #4163: all of them want some notion of “session title” metadata. The specific twist here is: auto-generated titles for live tab management (multi-session) and also for codex resume.

Suggestion for a minimal MVP that likely satisfies both:

  • Persist a title field in the session metadata (alongside the history).
  • - Default title heuristic: first meaningful user message (trim + truncate to ~40 chars).
  • - - Add a lightweight /title (or similar) action to regenerate (heuristic again, or optionally model-based later), plus manual rename later.

That gets the UX win without requiring an LLM call up front, and reduces fragmentation if we treat auto-titling as the default behavior for “named sessions” rather than a separate feature.

CanRau · 5 months ago

Just recently switched from GitHub Copilot and their CLI changes the title also to include a bell emoji (🔔) if the task has completed or it requires your input and also makes the terminal icon in macOS dock jump, really missing those 🥹

JohannesGESchmidt · 4 months ago

Please add the terminal title feature!
Turns out this is the hardest thing about moving from Claude to Codex

etraut-openai contributor · 3 months ago

This feature will be included in the next release.

moritonal · 3 months ago

Just noting, the end result is currently a bit strange. I previously had a script that let my Codex update the terminal title itself, worked great in VSCode. Now however Codex is updating the title (and outputting progress) itself, but that's overriding the previously piped title. It's not however using the Codex renamed conversation title, instead it's just outputting a blank which causes VSCode to override with it's own default terminal.

JohannesGESchmidt · 3 months ago

@etraut-openai The feature in it's current form is worse than before - before we could at least tell Agents.md that codex runs the environments terminal title comand to set the current task

this way if I babysit 10 instances i know at a glance -> fix Issue420 / review PR987 / Implement Feature Foo / Security Review

now it's a mix of those redundant infos:

<img width="772" height="143" alt="Image" src="https://github.com/user-attachments/assets/46a92d44-2378-4f3a-9b8c-51ac5de51a19" />

none of those challenges the model to provide value - it's all info that is predetermined through the environment or visible through other idle/busy indicators - but nothign unique

give us at least the option to switch it off fully
also the braile spinner animation is quiete expensive on the environment

etraut-openai contributor · 3 months ago

@JohannesGESchmidt, please open a new feature request.