What happened
Maka detects a conversation produced by Codex Desktop 0.149 and reports a successful import. However, opening the newly created task displays the empty-conversation state instead of the imported transcript.
The source rollout contains the user prompt, reasoning, and final assistant answer.
Expected behavior:
- The imported task displays the user, reasoning, and assistant messages.
- Each message appears exactly once.
- The task title is derived from the first user message.
Root cause:
Codex Desktop 0.149 writes presentation messages as event_msg records whose payload.type is item_completed. The nested item.type can be UserMessage, Reasoning, or AgentMessage.
CodexSessionAdapter currently recognizes only the legacy user_message, agent_message, and agent_reasoning event shapes. It intentionally ignores presentation-message mirrors in response_item to prevent duplicate imports. Consequently, newer rollouts contribute terminal turn state but no visible transcript messages.
简体中文
Maka 可以检测到 Codex Desktop 0.149 创建的对话,并显示导入成功,但打开新创建的任务后,页面仍然显示空会话状态,没有展示导入的消息。
原始 rollout 文件中实际包含用户消息、推理过程以及最终回复。
预期行为:
- 导入后的任务可以显示用户消息、推理消息和助手回复。
- 每条消息只出现一次。
- 任务标题从第一条用户消息中生成。
问题原因:
Codex Desktop 0.149 使用 payload.type 为 item_completed 的 event_msg 记录保存展示消息,其内部 item.type 可能为 UserMessage、Reasoning 或 AgentMessage。
目前 CodexSessionAdapter 只识别旧版的 user_message、agent_message 和 agent_reasoning 事件。为了避免重复导入,它又会忽略 response_item 中的展示消息镜像,因此新格式的会话最终只导入了结束状态,没有导入可见消息。
How to reproduce
- Use Codex Desktop 0.149 to create and complete a conversation containing at least one user message and one assistant response.
- Build and run Maka from the current
main branch.
- Open Settings → Activity → Import tasks.
- Select Codex and import the conversation.
- Open the newly imported task.
Actual result:
The task is created, but its transcript is blank and the main panel displays the empty-conversation state.
Expected result:
The imported user, reasoning, and assistant messages are visible exactly once.
简体中文
- 使用 Codex Desktop 0.149 创建并完成一个至少包含一条用户消息和一条助手回复的对话。
- 从当前
main 分支构建并启动 Maka。
- 打开 设置 → 活动 → 导入任务。
- 选择 Codex 并导入该对话。
- 打开刚导入的任务。
实际结果:
任务已经创建,但对话内容为空,主页面仍然显示空会话状态。
预期结果:
导入的用户消息、推理过程和助手回复均能正常显示,并且每条只显示一次。
Environment
- Maka screenshot commit:
9a661a1
- Confirmed affected current
main commit: 4acfa2693
- Codex Desktop rollout version:
0.149.0-alpha.4.1
- Codex source:
vscode
- OS: macOS 26.5.2 (25F84), arm64
- Surface: Desktop, source build
- Node.js: v22.23.1
- npm: 10.9.8
Logs, screenshots, or additional context

What happened
Maka detects a conversation produced by Codex Desktop 0.149 and reports a successful import. However, opening the newly created task displays the empty-conversation state instead of the imported transcript.
The source rollout contains the user prompt, reasoning, and final assistant answer.
Expected behavior:
Root cause:
Codex Desktop 0.149 writes presentation messages as
event_msgrecords whosepayload.typeisitem_completed. The nesteditem.typecan beUserMessage,Reasoning, orAgentMessage.CodexSessionAdaptercurrently recognizes only the legacyuser_message,agent_message, andagent_reasoningevent shapes. It intentionally ignores presentation-message mirrors inresponse_itemto prevent duplicate imports. Consequently, newer rollouts contribute terminal turn state but no visible transcript messages.简体中文
Maka 可以检测到 Codex Desktop 0.149 创建的对话,并显示导入成功,但打开新创建的任务后,页面仍然显示空会话状态,没有展示导入的消息。
原始 rollout 文件中实际包含用户消息、推理过程以及最终回复。
预期行为:
问题原因:
Codex Desktop 0.149 使用
payload.type为item_completed的event_msg记录保存展示消息,其内部item.type可能为UserMessage、Reasoning或AgentMessage。目前
CodexSessionAdapter只识别旧版的user_message、agent_message和agent_reasoning事件。为了避免重复导入,它又会忽略response_item中的展示消息镜像,因此新格式的会话最终只导入了结束状态,没有导入可见消息。How to reproduce
mainbranch.Actual result:
The task is created, but its transcript is blank and the main panel displays the empty-conversation state.
Expected result:
The imported user, reasoning, and assistant messages are visible exactly once.
简体中文
main分支构建并启动 Maka。实际结果:
任务已经创建,但对话内容为空,主页面仍然显示空会话状态。
预期结果:
导入的用户消息、推理过程和助手回复均能正常显示,并且每条只显示一次。
Environment
9a661a1maincommit:4acfa26930.149.0-alpha.4.1vscodeLogs, screenshots, or additional context
9a661a1; the same parsing gap remains on currentmainat4acfa2693.