You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Cannot resume Codex Desktop paginated history in native chat on Windows #27385
On Orca 1.4.224, an existing Codex Desktop conversation appears in Agent Session History, but selecting “Resume in New Native Chat” fails with the Chinese message “无法确认聊天连接。” (“Chat connection could not be confirmed.”).
Claude conversations can be restored successfully on the same computer.
Environment
OS: Windows, local runtime, no WSL
Orca: 1.4.224
Codex CLI used for recovery and diagnostics: 0.162.0-alpha.2
Authentication: ChatGPT account
Codex history mode: paginated
The Orca workspace matches the original conversation’s project directory.
Steps to reproduce
Open a project in Orca that has an existing Codex Desktop conversation.
Find the conversation in Agent Session History.
Select “Resume in New Native Chat.”
Observe the connection error instead of the restored conversation.
Observed diagnostics
Local investigation found two potential obstacles in the native-chat import path:
The legacy JSONL importer has a 16 MiB size limit. The original conversation’s rollout file is 52,938,660 bytes, approximately 50.5 MiB.
A fork of the paginated conversation stores inherited history through a history reference rather than duplicating all messages in its own JSONL file. Attempting to attach this fork to native chat returned:
The conversation itself is readable through Codex’s app-server API. Full-history retrieval recovered 53 turns and 1,255 history items. The recovered fork’s history matched the original, and it successfully continued the conversation in Orca’s terminal.
This suggests a compatibility gap in native-chat import, although the generic UI error alone does not identify which check failed first.
Separate writer-lock behavior
Resuming the original conversation in the terminal also showed:
“This conversation is open in another app.”
The original thread was still held by the Codex backend belonging to ChatGPT Desktop. Creating an independent fork using Codex’s built-in f fork action resolved that conflict and allowed terminal use. Native-chat import remained unsuccessful.
Expected behavior
Orca should restore paginated Codex history, including inherited fork history, using the supported Codex history APIs rather than requiring a complete standalone JSONL transcript.
If restoration is blocked by a writer lock, transcript size limit, or unsupported history format, the UI should explain the specific cause and offer an appropriate recovery action.
Is there a supported version or workaround for restoring these conversations into native chat? If not, could support for paginated history and history-reference forks be added?
Activity
AmethystLiang commentedon Oct 12, 2026
Thanks for reporting. Looking into it