[Windows][26.814] Archiving a local chat fails after a delay and the chat remains active

What version of the Codex App are you using (From “About Codex” dialog)?

Windows package 26.814.5167.0; app-server client 26.814.41407

What subscription do you have?

ChatGPT Work (organization-managed; exact subscription tier is not shown in this view)

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

Archiving a normal local chat no longer works after the recent Windows app update. After clicking Archive, the app waits and then shows the localized error toast: 聊天归档未成功 (Chat archive failed). The chat remains in the active sidebar and the Archived chats list remains empty. Local diagnostics show that the UI dispatches thread/archive, then tears down the thread listener, but never receives a thread/archived notification and the archive is not persisted. The underlying session is still present, so this appears to be an archive-operation failure rather than data loss.

What steps can reproduce the bug?

1. Open an existing, idle local Codex chat on Windows.
2. Choose Archive from the chat menu.
3. Wait several seconds.
4. Observe the Chat archive failed toast.
5. Confirm that the chat remains active and Archived chats is empty.

Reproduced on 4 out of 4 idle local chats. No Remote SSH workspace or active automation was involved.

What is the expected behavior?

The archive operation should complete, the chat should move out of the active sidebar into Archived chats, and it should be restorable later.

Additional information

This appears to be a regression: local logs from app version 26.810.52044 emitted thread/archived and thread/status/changed for the same operation. In 26.814.41407, the request is logged but those success events are absent. Related issues for Remote SSH cross-filesystem moves and self-archiving automations do not match this local, user-initiated failure. The original screenshot is intentionally not attached because it contains private workspace and chat titles.

Start by tracing the local Windows archive flow from the thread/archive dispatch through listener teardown, using the logs described in the issue. Compare the success events emitted in version 26.810.52044 with their absence in 26.814.41407. Done means archiving completes, the chat leaves the active sidebar, appears in Archived chats, and can be restored.