›_ Codex Issues
Codex Issues / #21803

Feature request: Cross-device sync for Codex Projects and Chats

Open 💬 6 comments Opened May 8, 2026 by HezLUO
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What feature are you requesting?

I would like Codex to support cross-device continuity for Projects and Chats when signed in with the same OpenAI account.

For example, I use Codex across two Mac computers. Ideally, I could start a Codex Project or Chat on one Mac, then open Codex on another Mac with the same account and continue the same Project or Chat from where I left off.

Why is this useful?

Many developers regularly switch between a desktop and a laptop. Today, Codex sessions and project context feel tied to the local machine, which means switching devices requires manually recreating context, syncing notes, or relying on external workarounds.

My ideal experience would be similar to ChatGPT conversation continuity: recent Codex Projects, Chats, task state, and high-level working context would be available across trusted devices.

I understand that local filesystem paths, repositories, terminal state, and approval settings may need to remain device-specific. But it would still be very valuable to sync or restore:

  • Conversation history
  • Project metadata
  • Current task state
  • Recent working context
  • Associated repository information
  • Session summaries or checkpoints

Possible implementation options

A native account-level sync feature would be ideal.

If full native sync is not currently planned, I would also be grateful for any official API, SDK, MCP integration, or supported import/export mechanism that would allow users to build this functionality themselves.

For example, an official way to access, export, restore, or synchronize Codex sessions across trusted devices would make it possible to build a personal “session hub” or workflow manager around Codex.

Related discussions / issues

This request is related to, but more specifically focused on cross-device Codex continuity:

Additional context

Thank you for building Codex. It has been very helpful, and cross-device continuity would make it much smoother for users who regularly move between multiple computers.

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #20757

Powered by Codex Action

ahmojo · 2 months ago

I ran into the same cross-device/local-session portability problem and built a small unofficial workaround: [codex-sync](https://github.com/ahmojo/Codex_Sync).

It does not solve native account-level sync, and it is not affiliated with or endorsed by OpenAI. It is meant as a conservative manual handoff tool for trusted devices while native cross-device continuity is not available.

What it does:

  • exports local Codex project sessions into a .codexbundle
  • lets you inspect the bundle before importing
  • imports sessions on another machine without writing Codex SQLite
  • optionally maps project paths with --map-cwd OLD=NEW when the project lives at a different path on the destination machine
  • uses no cloud, no account, no server, and no background daemon

The safety model is intentionally narrow: normal import is byte-for-byte, existing sessions are never silently overwritten, bundle checksums are verified before import, and --map-cwd only rewrites the canonical cwd field inside the session_meta line for matching plain .jsonl sessions.

Sharing it here in case it helps others who are moving between a desktop and laptop and need a local-first workaround until there is an official/importable cross-device story.

d-jiao · 1 month ago

I fully support this proposal. It will be an incredibly useful feature.

DigiBeter · 11 days ago

I’m affected by this in a Windows ↔ macOS workflow, and basic chat-history sync is not enough. The current split between account-level chats and device-local Codex projects makes working across multiple PCs effectively unworkable.

The expected behavior is native, bidirectional synchronization across trusted devices, including:

  • local Codex thread/session history and current task state;
  • project associations, with per-device path mapping;
  • working branch/checkout state and Codex-generated files;
  • project-level .codex/ configuration and AGENTS.md context;
  • queued offline changes, sync status, conflict detection, and explicit conflict resolution.

When Codex changes a local project on one computer, it should be able to create/push a recoverable checkpoint and let another trusted computer automatically pull/restore it. Changes made from either device should propagate back. Users should not have to combine manual Git operations with copying hidden session files and rebuilding project context.

A safe implementation could use Git-backed checkpoints for repository content, encrypted account sync for session/task metadata, platform-specific path mapping, and automatic exclusion of credentials, environment files, and other secrets.

Without end-to-end local-to-local continuity, switching between Windows and macOS means reconstructing context, manually transporting files and settings, and risking divergent work. Please treat full cross-device continuity for local Codex work as core product functionality, not only as conversation-history sync.

dkwolf1 · 4 days ago

maybe it's an idea to further develop this https://github.com/dkwolf1/Codex-Lifeboat, with network options?

CCCCY-ci · 4 days ago

This is exactly the workflow I wanted too.

I ended up building an open-source workaround called CtxHop. It syncs Codex sessions through your own S3/R2 storage, so I can stop on my desktop and resume the same session on my laptop.

It’s obviously not a replacement for native account-level sync, but it works pretty well as a personal session hub for now:

https://github.com/CCCCY-ci/ctxhop