codex - ✅(Solved) Fix Codex resume does not show the id in 0.121 [1 pull requests, 2 comments, 2 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#18313Fetched 2026-04-18 05:56:14
View on GitHub
Comments
2
Participants
2
Timeline
10
Reactions
0
Author
Timeline (top)
labeled ×5commented ×2unlabeled ×2cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #18440: Use thread IDs in TUI resume hints

Description (problem / solution / changelog)

Summary

Fixes #18313.

Recent TUI resume breadcrumbs could print a thread title instead of the stable thread UUID. For sessions whose title was auto-derived from the first prompt, that made the suggested codex resume command look like it should resume a long prompt rather than the session ID.

This updates the TUI and CLI post-exit resume hints, plus the in-session summary shown when switching/forking threads, to always use the stable thread ID for these recovery breadcrumbs. Explicit name-based resume support remains available elsewhere.

Changed files

  • codex-rs/cli/src/main.rs (modified, +4/-4)
  • codex-rs/tui/src/app.rs (modified, +5/-6)
  • codex-rs/tui/src/main.rs (modified, +3/-2)
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.121

What subscription do you have?

Pro

Which model were you using?

No response

What platform is your computer?

No response

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

VSCode

What issue are you seeing?

If I write /fork or press ctrl+c, it now often displays the following message

To continue this session, run codex resume 'Review the current code changes (staged, unstaged, and untracked files) and provide prioritized findings.' instead of codex resume 'some-id-here-'

What steps can reproduce the bug?

I'm not really sure. It happens only sometimes in long sessions, when pressing ctrl+c or typing /fork.

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue may be resolved by using the correct codex resume command with the provided session ID instead of the default one.

Guidance

  • Verify that the codex resume command is being used with the correct session ID, as indicated in the error message.
  • Try to reproduce the issue and check if the error message provides a specific session ID that can be used to resume the session.
  • If the issue persists, try to identify any patterns or common factors that may trigger the error, such as long sessions or specific actions.
  • Consider providing more information about the expected behavior and additional context to help troubleshoot the issue.

Notes

The issue seems to be related to the codex resume command and the session ID, but more information is needed to provide a definitive solution.

Recommendation

Apply workaround: use the correct codex resume command with the provided session ID, as this may resolve the issue and allow the session to continue.

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

codex - ✅(Solved) Fix Codex resume does not show the id in 0.121 [1 pull requests, 2 comments, 2 participants]