Ctrl+C after resuming a session with no new turn does not print the resume command

What version of Codex CLI is running?

codex-cli 0.118.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.4

What platform is your computer?

Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64

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

VS Code integrated terminal (WSL2 Ubuntu 22.04)

What issue are you seeing?

If I resume an existing interactive session and then exit with Ctrl+C before sending any new prompt, Codex does not print the usual:

To continue this session, run codex resume ...

This is different from the case where I resume a session, send one new prompt, and then exit: in that case the footer does appear.

This makes the resume flow unnecessarily tedious when I have many saved sessions and use codex resume <thread-name> as a quick way to reopen one, inspect it, and exit again. Without the footer, I have to go back through the picker each time.

I verified this on 0.118.0 and it appears to be tied to zero new token usage during the current resumed process, not only to the existing WSL SIGINT bug.

Related but distinct from:

• #9448, which is about WSL2 sometimes exiting via SIGINT before the normal footer can be printed even when token usage is non-zero.

What steps can reproduce the bug?

1. Start or identify an existing Codex CLI session that already has a thread name or thread id.
2. Resume it with either:

• codex resume <thread-name>
• or select it from the normal codex resume picker

1. Do not send any new prompt after resuming.
2. Press Ctrl+C to exit.
3. Observe that no codex resume ... continuation command is printed.

Control case:

1. Resume the same session.
2. Send one small prompt.
3. Press Ctrl+C.
4. Observe that the footer is printed normally.

What is the expected behavior?

Codex should print the continuation command whenever the current interactive session is resumable, even if no new prompt was sent after resume.

At minimum, the footer should still include:

To continue this session, run codex resume <thread-name-or-id>

This is especially useful when resuming an existing session only to inspect context and then exit again.

Additional information

This seems to be a separate behavior from the WSL Ctrl+C/SIGINT issue in #9448.

The current CLI behavior appears to suppress all exit footer lines when the current process has zero token usage, which also suppresses the resume command for resumed sessions that remain perfectly resumable.