Feature Request: Synchronization of Codex Threads and Session Context Across Devices

[jorgengk]

Feature Request: Synchronization of Codex Threads and Session Context Across Devices

I frequently work across multiple machines (for example a work computer and a home computer) while using Codex to develop software. Currently, Codex threads and session context appear to be tied to the local environment of the machine where the session was started. As a result, when switching devices, the Codex conversation history, reasoning context, and task progress are not available on the second machine.

This creates unnecessary friction in multi-device workflows. When moving from one machine to another, it is often necessary to recreate the context manually, re-explain the architecture of the project, or restart tasks that were already underway.

A very valuable improvement would be the ability to synchronize Codex sessions across devices associated with the same user account.

Ideally this feature would include:

Synchronization of Codex conversation threads across devices

Preservation of task history and reasoning context

Visibility of active or recent Codex sessions from other machines

The ability to continue an existing Codex session seamlessly on another device

Optional cloud storage of session state tied to the user's account

Even if local file paths or environments differ between machines, retaining the conversational context and high-level task history would significantly improve usability. The repository and environment could then be reloaded locally while still preserving the reasoning history of the session.

For users who frequently switch between machines, this would make Codex feel like a persistent development partner rather than a tool that resets context when changing devices.

Thank you for considering this feature.

[etraut-openai]

Thanks for the suggestion. This is a discussion forum. If you'd like to file a feature request, please use the issue tracker instead. We generally prioritize features based on community upvotes in the issue tracker.

[aniruddhaadak80]

The multi-device workflow you describe is increasingly common, and preserving reasoning context across machines would genuinely improve the development experience. The hard part seems to be balancing cloud persistence with local environment differences, especially when paths and repository layouts vary.

To clarify the requirement, how often do you switch devices during active work? It would also help to know whether selective sync is enough, or if you need every session and recent thread to follow you across every machine automatically.

[Nyrok]

The "recreate context manually" problem when switching devices is partly a session sync problem, but also a prompt structure problem.

When your task context lives as typed blocks, role, context, objective, constraints, rather than embedded in conversation history, you can carry it across devices as a plain file. The session history does not need to follow you. The structured prompt becomes the portable source of truth.

That is how I approach cross-machine continuity with flompt, a visual prompt builder that decomposes prompts into 12 semantic blocks and compiles to Claude-optimized XML. Paste the compiled prompt on any machine, in any tool, and you are back in context. Open-source: github.com/Nyrok/flompt

[Companionh]

Hi, I thought the exact same thing as you did and I've been spending the last week trying to implement a codex session/working environment sync across multiple devices.

The project is currently in experimental alpha but the features for sharing all codex sessions work properly and get updated with each turn.

https://github.com/Companionh/codex-workspace-sync