Standalone codex-tui no longer prints resume hint on normal exit
Resolved 💬 5 comments Opened Apr 10, 2026 by oxysoft Closed Apr 11, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
The standalone codex-tui binary no longer prints the exit-time resume hint (To continue this session, run codex resume ...) on a normal exit, even though the main codex CLI still does.
This looks like entrypoint drift rather than the broader SIGINT/abnormal-exit cases.
Repro
- Start a session with
codex-tui - Use it enough to materialize a thread id
- Exit normally
- Observe that only token usage is printed, with no
codex resume ...hint
Expected
Normal codex-tui exits should print the same resume hint as codex, using the thread name when available and otherwise the thread id.
Root Cause
codex-rs/cli/src/main.rs still formats and prints the resume hint on exit, but codex-rs/tui/src/main.rs only printed token usage and dropped the shared resume-command behavior.
Fix Ready
I have a branch with a minimal fix that restores the hint in codex-tui, aligns fatal-exit handling with the main CLI entrypoint, and adds unit coverage.
- Branch:
oxysoft/fix-tui-exit-resume-hint - Commit:
ad6dd801586d7032fbc4f6193533420ab675b1a8
Validation
just fmtcargo test -p codex-tui
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Are you running the latest released (0.118.0) or a prerelease alpha, or are you building from source? We've fixed some related bugs since 0.118.0.
Running v0.118.0
I'm noticing now that the message does print in some cases but not 100% of the time. I think it's conversations started with
codex resumethat don't printOK, thanks. I'll look into it.
This will be addressed in the next release.