Improve resume hint rendering

What version of Codex CLI is running?

0.121.0

What subscription do you have?

Resume hint is rendered like conversation content but behaves like transient pane UI

Which model were you using?

gpt-5.4 xhigh, gpt-5.4 high ....

What platform is your computer?

Microsoft Windows NT 10.0.26300.0 x64

What terminal emulator and version are you using (if applicable)?

Windows Terminal (PowerShell / ConsoleHost), version 1.25.923.0

What issue are you seeing?

During pane/session recovery, Codex TUI sometimes renders a line like:

To continue this session, run codex resume 019da974-9238-7720-9829-f578a5c8e808

The problem is that this line is displayed inline in the same visual flow as conversation-stage content / diagnostic text, so
it looks like durable session history or a stable chat artifact.

Later, when I go back and inspect the conversation/session history, that line may no longer be present or recoverable. This
makes it unclear whether the shown resume id is actual persisted session state, or just transient pane/runtime UI.

From the UI, it is easy to interpret this as part of the conversation stage, but from later behavior it appears to behave like
ephemeral session/pane state instead of durable history.

In the same screen, the resume hint is rendered together with runtime/status messages such as MCP startup warnings and the TUI
footer/status block, which makes the boundary between persisted chat content and transient runtime UI unclear.

What steps can reproduce the bug?

1. Use Codex CLI in a longer session on Windows Terminal.
2. Interrupt, return to, or otherwise recover a prior pane/session state.
3. Observe that Codex may render a line like:

To continue this session, run codex resume <id>

1. Continue working, switch context, or revisit the earlier conversation/session stage later.
2. Observe that the resume hint may no longer be present/recoverable in later history lookup, even though it previously

appeared inline like conversation content.

Example resume id shown in the UI:
019da974-9238-7720-9829-f578a5c8e808

This appears to happen around session/pane recovery boundaries rather than during normal steady-state chat rendering.

What is the expected behavior?

Resume hints should either:

1. be clearly rendered as transient UI banners outside the conversation flow, or
2. be persisted and recoverable if they are shown inline in a conversation-like surface.

The current behavior makes the resume hint look like stable conversation/session history even though it does not appear to
behave that way afterward.

Additional information

• I have a screenshot showing the resume hint rendered inline together with:
• conversation-stage diagnostic text
• local taskpane/runtime investigation notes
• MCP startup warnings
• the TUI footer/status block

• That mixed rendering is why this looks more like a UX/persistence-boundary bug than a backend import/link failure.

• Related but not identical issue:

#18313 "Codex resume does not show the id in 0.121"
My case is different: the UI does show an id, but it behaves like transient pane UI while looking like durable chat/session
content.

<img width="752" height="1016" alt="Image" src="https://github.com/user-attachments/assets/6714c79b-f756-4718-bf82-06e973433682" />