[app][Windows][26.721.4979.0] Voice shortcut forks chat and archives the original task

Summary

On Codex Desktop for Windows, accidentally invoking the Toggle voice chat native shortcut while viewing an existing project task created a separate realtime-voice task titled Forked Voice Chat and then archived the original task.

The original task disappeared from normal task history and initially appeared to have been deleted. Its history was still present in the backend/archive and became accessible again after manually locating and unarchiving it.

This is distinct from the provisional voice task itself disappearing: the task that was archived was the pre-existing, long-running project task.

Environment

• Codex Desktop package: OpenAI.Codex 26.721.4979.0 (Windows Store)
• Platform: Windows 11 Pro Insider Preview, x64, version 10.0.26220
• Authentication: ChatGPT
• Original task ID: 019f8205-4246-7650-92fd-81121cb9f6be
• Voice-created task ID: 019fb03f-de05-7710-af91-c6f6fac85cf0
• Voice-created task source: realtime_voice

No conversation contents or project source are included in this report.

Steps that produced the problem

1. Open an existing, long-running project task.
2. Accidentally invoke the native Toggle voice chat shortcut.
3. Codex creates a separate projectless realtime-voice task titled Forked Voice Chat.
4. Leave voice and attempt to return to the original task.
5. Observe that the original task cannot be found in normal task history.
6. Open the archived-task view.
7. Observe that the original task was archived.
8. Manually unarchive it; the original task and history become available again.

Deterministic local log evidence

Sanitized Codex Desktop log sequence (UTC):

2026-07-29T23:40:06.006Z realtime_session_started
  threadId=019fb03f-de05-7710-af91-c6f6fac85cf0
  realtimeSessionId=null

2026-07-29T23:40:07.784Z realtime_session_updated
  realtimeSessionId=rtc_...

2026-07-29T23:40:21.627Z Archive requested
  conversationId=019f8205-4246-7650-92fd-81121cb9f6be
  source=native_accelerator

2026-07-29T23:40:24.339Z thread/archive succeeded
  conversationId=019f8205-4246-7650-92fd-81121cb9f6be
  errorCode=null

2026-07-29T23:50:39.155Z Unarchive requested
  conversationId=019f8205-4246-7650-92fd-81121cb9f6be

2026-07-29T23:50:39.168Z Unarchive succeeded
  conversationId=019f8205-4246-7650-92fd-81121cb9f6be

The important detail is that the voice session belongs to the new task, while the native-accelerator archive request targets the original task.

After the archive operation, normal task listing showed the voice-created task but not the original. Direct backend inspection confirmed that the original history was retained and later restored successfully.

Actual behavior

Starting/toggling voice created a separate task and caused the original active task to be archived without the user choosing Archive.

This looks like data loss until the user discovers the archived-task view and manually restores the task.

Expected behavior

Creating or toggling a realtime voice task must not change the archive state of the task from which voice was invoked.

If a voice fork is created, Codex should preserve the original task exactly as-is and provide a clear way to return to it.

Impact

This can make an important long-running project conversation appear permanently lost immediately after an accidental shortcut press. Users may not know that the task was silently archived, may begin duplicate work, or may assume that conversation history was deleted.

Possible failure area

The log entry source=native_accelerator suggests an accelerator-routing or voice lifecycle bug. The archive command appears to have been dispatched to the original conversation while the realtime overlay/new voice task was active.

Related open issues

• #35907 — Toggle voice chat creates dead history entries on Windows
• #35252 — Realtime voice provisional-thread startup/archive cleanup failure on the same app version
• #35103 — Voice mode thread disappears after inactivity timeout
• #25463 — Project threads disappear from normal views while backend history remains readable

Those reports overlap with the voice/session lifecycle and visibility symptoms, but I did not find one documenting the original pre-existing task being archived by the native voice-shortcut flow.