codex - 💡(How to fix) Fix Make Codex CLI sessions available in Codex desktop history [3 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#21079Fetched 2026-05-05 05:53:44
View on GitHub
Comments
3
Participants
3
Timeline
6
Reactions
1
Timeline (top)
commented ×3labeled ×3

Root Cause

CLI and desktop are part of the same Codex product and account experience. Users expect Codex-native sessions to move between terminal and desktop more seamlessly than imported third-party sessions. This would make it easier to continue work across the CLI and desktop app without manually finding session IDs.

RAW_BUFFERClick to expand / collapse

What feature would you like to see?

Make local Codex CLI sessions available as first-class threads in Codex desktop history, or provide an explicit “Import Codex CLI history” action.

Current behavior

Codex desktop onboarding successfully imported Claude Code history into the app. Native Codex CLI sessions are stored locally and resumable from the CLI, but they do not appear to be surfaced in Codex desktop history the same way.

Verified locally:

  • codex resume --all can see prior Codex CLI sessions.
  • Resuming a specific CLI session by ID works.
  • The resumed session loaded the prior transcript and accepted a new prompt.
  • Codex desktop history does not appear to show those Codex-native CLI sessions as first-class desktop threads.

Expected behavior

Codex desktop should index and display local Codex CLI sessions automatically, or offer an explicit import flow for Codex CLI history.

Why this matters

CLI and desktop are part of the same Codex product and account experience. Users expect Codex-native sessions to move between terminal and desktop more seamlessly than imported third-party sessions. This would make it easier to continue work across the CLI and desktop app without manually finding session IDs.

Environment

  • Codex CLI: 0.128.0
  • Platform: macOS
  • Auth mode: ChatGPT login

extent analysis

TL;DR

To make local Codex CLI sessions available in Codex desktop history, consider implementing an explicit "Import Codex CLI history" action or modifying the desktop app to automatically index and display local CLI sessions.

Guidance

  • Investigate the current data storage and synchronization mechanisms between Codex CLI and desktop to understand why local CLI sessions are not being surfaced in desktop history.
  • Explore adding an "Import Codex CLI history" feature to the desktop app, allowing users to manually import their local CLI session history.
  • Consider modifying the Codex desktop onboarding process to automatically import local Codex CLI session history, similar to how it currently imports Claude Code history.
  • Review the codex resume --all command and its interaction with the desktop app to identify potential integration points for surfacing local CLI sessions.

Notes

The solution may require changes to both the Codex CLI and desktop app, and careful consideration of user authentication and data synchronization is necessary to ensure a seamless experience.

Recommendation

Apply a workaround by implementing an explicit "Import Codex CLI history" action in the desktop app, as this seems to be a more straightforward solution compared to modifying the underlying data storage and synchronization mechanisms.

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…

FAQ

Expected behavior

Codex desktop should index and display local Codex CLI sessions automatically, or offer an explicit import flow for Codex CLI history.

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 - 💡(How to fix) Fix Make Codex CLI sessions available in Codex desktop history [3 comments, 3 participants]