{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidrykpkzvmohy6p3abunzr4f57ogxw4yc2d4taqommo4e35hdjona",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mkgyjvzam5z2"
  },
  "path": "/t/legacy-codex-local-jsonl-session-import-into-cloud-synced-codex-desktop/1379835#post_1",
  "publishedAt": "2026-04-27T01:12:39.000Z",
  "site": "https://community.openai.com",
  "textContent": "Hello OpenAI/Codex Support,\n\nI am requesting a supported migration/import path for legacy Codex local sessions into the new cloud-synced Codex Desktop app.\n\nMy current situation:\n\n  * I have 269 legacy Codex sessions stored locally as `.jsonl` files.\n\n  * Some individual session files are over 180MB.\n\n  * I upgraded to the new Codex Desktop app, package `com.codexorbit.app`, version family `v26.422+`.\n\n  * The new app appears to use cloud-synced thread history for the Desktop sidebar, with local SQLite caching in `orbit.db`, rather than directly listing legacy local `.jsonl` sessions.\n\n\n\n\nDesired feature:\n\nPlease provide a supported way to import local legacy Codex `.jsonl` sessions so they appear as native, sidebar-visible Codex Desktop threads under my account.\n\nWhy current workarounds are insufficient:\n\n  * SQLite patching is not viable. Injecting records into `orbit.db` does not create valid account-owned cloud thread IDs, and the app’s sync layer appears to purge or reject records that do not exist on the backend.\n\n  * Drag-and-drop file attachment is useful for referencing old context, but it does not preserve 269 individual threads, titles, timestamps, project grouping, tool history, or sidebar continuity.\n\n  * External local viewers can make the archive searchable, but they do not solve migration into the native Codex Desktop workflow.\n\n\n\n\nA useful migration feature could be one of:\n\n  * A Codex Desktop “Import legacy sessions” command.\n\n  * A CLI migration tool that uploads local `.jsonl` sessions into my account as Codex cloud threads.\n\n  * A documented admin/support-assisted import process.\n\n  * A local-only legacy sidebar mode that indexes old `.jsonl` sessions without conflicting with cloud sync.\n\n\n\n\nI am happy to provide sanitized schema samples, file-size distribution, and logs if helpful. The key requirement is a supported import path that does not require unsupported SQLite edits or private backend API manipulation.\n\nThank you.",
  "title": "Legacy Codex local JSONL session import into cloud-synced Codex Desktop"
}