Session transfer between Codex CLI and Codex Desktop
What variant of Codex are you using?
APP and CLI
What feature would you like to see?
Session transfer between Codex CLI and Codex Desktop
Problem
When I start a session through Codex CLI, it does show up in Desktop's history, but it lands there as a regular Work chat — not as a Codex session tied to the matching local project. That breaks the flow of moving between CLI and Desktop.
Here's the workflow I'd like: I start from the terminal:
cd my-projectcodex
Then I open Codex Desktop, find that same session under the corresponding Codex project, review or continue the conversation there, and at some point go back to the terminal to pick up that same session again.
Proposed behavior
Codex Desktop could recognize sessions started via CLI and associate them with the matching local project/repository. Ideally the session would carry over things like:
Working directory (cwd)
Git repository
Current branch
Conversation/session ID
Session origin (CLI or Desktop)
Desktop could also offer a "Continue in terminal" action that resumes that same Codex session from the right working directory.
The workflow would look like:
Codex CLI
↓Codex Desktop / Project
↓Same session
↓Continue in terminal
Why this would help
CLI and Desktop cover different but complementary workflows. CLI is great while I'm actively coding, and Desktop is better for reviewing longer conversations, thinking through implementation decisions, and picking up past work. Treating both as interfaces into the same Codex session, instead of separate conversation environments, would make switching between them a lot more natural.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
duplicated