Clarify resume hints for renamed threads

[kchung1995]

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:

1. /rename displays correct guide (unless we change the behaviour).
2. /exit also 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.

[etraut-openai]

Thanks for the suggestion. This will be included in a future update.

[Alek2077]

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:

1. This still reads like a pasteable command hint, especially with the current inline/cyan rendering.
2. If resuming by thread name directly, multi-word names require shell quoting:
   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 thread
• codex 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.