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 fmt
cargo test -p codex-tui
Summary
The standalone
codex-tuibinary no longer prints the exit-time resume hint (To continue this session, run codex resume ...) on a normal exit, even though the maincodexCLI still does.This looks like entrypoint drift rather than the broader SIGINT/abnormal-exit cases.
Repro
codex-tuicodex resume ...hintExpected
Normal
codex-tuiexits should print the same resume hint ascodex, using the thread name when available and otherwise the thread id.Root Cause
codex-rs/cli/src/main.rsstill formats and prints the resume hint on exit, butcodex-rs/tui/src/main.rsonly 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.oxysoft/fix-tui-exit-resume-hintad6dd801586d7032fbc4f6193533420ab675b1a8Validation
just fmtcargo test -p codex-tui