codex - ✅(Solved) Fix Standalone codex-tui no longer prints resume hint on normal exit [1 pull requests, 4 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17303Fetched 2026-04-11 06:18:13
View on GitHub
Comments
4
Participants
3
Timeline
10
Reactions
0
Author
Timeline (top)
commented ×4labeled ×4cross-referenced ×1unlabeled ×1

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.

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.

PR fix notes

PR #17415: Restore codex-tui resume hint on exit

Description (problem / solution / changelog)

Addresses #17303

Problem: The standalone codex-tui entrypoint only printed token usage on exit, so resumable sessions could omit the codex resume footer even when thread metadata was available.

Solution: Format codex-tui exit output from AppExitInfo so it includes the same resume hint as the main CLI and reports fatal exits consistently.

Changed files

  • codex-rs/tui/src/main.rs (modified, +39/-6)
RAW_BUFFERClick to expand / collapse

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

  1. Start a session with codex-tui
  2. Use it enough to materialize a thread id
  3. Exit normally
  4. 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

extent analysis

TL;DR

The codex-tui binary can be fixed by applying the changes from the oxysoft/fix-tui-exit-resume-hint branch, which restores the exit-time resume hint.

Guidance

  • Review the changes in the oxysoft/fix-tui-exit-resume-hint branch to understand the specific modifications made to restore the resume hint in codex-tui.
  • Verify the fix by running cargo test -p codex-tui to ensure unit tests pass.
  • Check the formatting with just fmt to confirm code style consistency.
  • Test the codex-tui binary manually by following the repro steps to ensure the resume hint is printed on normal exit.

Example

No code snippet is provided as the issue already references a specific branch and commit with the fix.

Notes

The fix is specific to the codex-tui binary and does not affect the main codex CLI. The changes are targeted at restoring the exit-time resume hint and aligning fatal-exit handling.

Recommendation

Apply the workaround by merging or cherry-picking the changes from the oxysoft/fix-tui-exit-resume-hint branch, as it provides a tested and validated solution to the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING