Repository navigation
Clarify resume hints for renamed threads #23181
Description
What variant of Codex are you using?
CLI / TUI
What feature would you like to see?
When a thread is renamed, this message gets displayed:
"Thread renamed to {thread-name}, to resume this thread run codex resume {thread-name}"
Which does not work. In fact, duplicates among threads' names are allowed, so we cannot point a specific thread with its name. We have to give the thread id instead.
Also, regardless of renaming a thread, exiting the thread displays:
"To continue this session, run codex resume {thread-id}"
Which, I think, looks awkward.
I think we would need to polish a bit so:
/renamedisplays correct guide (unless we change the behaviour)./exitalso mentions the thread name if it's renamed.
For example, /rename may display
"Thread renamed to {thread-name}. To resume this thread run codex resume, then select {thread-name}({thread-id})"
/exit may display
"To continue this session, run codex resume, then select {thread-name} ({thread-id})".
Additional information
A screenshot for Codex guiding to run codex resume {thread-name}, which is tried and failed.
Activity
Clarify resume hints for renamed threads (#23234)
etraut-openai commentedon May 18, 2026
Thanks for the suggestion. This will be included in a future update.
Alek2077 commentedon May 20, 2026
Confirmed this is still confusing in codex-cli 0.132.0.
After renaming, Codex shows:
"Thread renamed to some thread name. To resume this thread run codex resume, then select some thread name (019e4473-0d50-7120-dbcb-280c0dfd51d3)"
Two problems remain:
codex resume 'some thread name'Without quotes, the command fails because the shell splits the title into multiple arguments.
So the message is better than the old incorrect
codex resume <thread-name>hint, but it still does not clearly explain the actual executable options:codex resume, then select the threadcodex resume <thread-id>codex resume '<multi-word thread name>'I also have a screenshot of the current rendering that makes the hint look even more like an executable command example.
Necmttn commentedon Jun 21, 2026
The hint should separate display name from stable resume id.
I would always show the UUID as the copyable command target, and treat the thread name as picker/search text. Example:
Thread renamed to "foo". Resume with codex resume <id>, or run codex resume and search "foo".That avoids shell-quoting bugs and duplicate-name ambiguity without removing the friendly name.
Generated with ax.
Clarify resume hints for renamed threads (openai#23234)
etraut-openai commentedon Jul 21, 2026
Merged PR #23234 directly addresses the issue: named threads show () in picker guidance, while unnamed threads retain direct codex resume guidance. Any copy or quoting polish can be a follow-up.