Unofficial local-first Codex session portability workaround

[ahmojo]

Maintainer disclosure: I built a small unofficial workaround for one narrow part of this problem: local Codex session portability between machines.

Project: https://github.com/ahmojo/Codex_Sync

It is called codex-sync. It does not provide native/account-level sync, does not sync with OpenAI’s cloud backend, and does not create cloud-backed thread IDs. It is also not affiliated with or endorsed by OpenAI.

What it does instead is local-first and manual:

• export local Codex project sessions into a .codexbundle
• inspect the bundle before importing
• dry-run an import before writing anything
• import rollout files into another local Codex home
• optionally use --map-cwd OLD=NEW when the project path differs on the destination machine

It never writes Codex SQLite; it only works with the local rollout files and lets Codex rebuild/reconcile its own index on the next scan.

Sharing here in case it helps people who want a conservative backup / handoff workflow across trusted devices while an official cross-device/session-sync story does not exist yet.

Important caveat: .codexbundle files can contain prompts, code, terminal output, absolute paths, and secrets, so they should be treated as sensitive local project data and not posted publicly.