[Windows] Drag-selecting assistant output intermittently reloads the renderer

What version of the Codex App are you using?

• Microsoft Store/MSIX package: 26.721.11231.0
• Internal app release: 26.721.81911
• Chromium: 150.0.7871.128

What platform is your computer?

Windows 11, build 10.0.26200, x64.

What issue are you seeing?

Dragging with the left mouse button to select text in an assistant Markdown response intermittently makes the Codex window flash, show a loading state, and reload the conversation UI.

The window does not close and the main Codex process does not restart. The visible behavior is consistent with an Electron renderer reload/recovery.

Steps to reproduce

1. Open a task in Codex Desktop for Windows.
2. Wait for an assistant response containing rendered Markdown text.
3. Drag across the response with the left mouse button to select text.
4. Repeat during normal use.

The issue is intermittent rather than 100% reproducible.

Expected behavior

Text remains selected and the current conversation stays visible without flashing, loading, or reloading.

Observed behavior

The UI flashes, briefly enters a loading state, and then reloads. Work in the task continues, but the renderer state is rebuilt.

Local evidence from one occurrence

All timestamps below are JST on 2026-07-31:

• 15:06:49.237: an app breadcrumb recorded interaction with rendered Markdown text.
• 15:06:52.189: a new Electron renderer process started.
• The main ChatGPT.exe process remained alive from 14:51:57.
• The GPU process remained alive from 14:51:58; it did not restart around the incident.
• No related Windows Application/WER crash event was recorded.
• Crashpad activity occurred around the renderer restart, but no dump was retained.
• The affected renderer used roughly 2.5 GB of working memory; telemetry recorded a peak renderer working set of 4,137,716 KB.
• Front-end state errors observed in the same app session included:
• Received item/started for unknown conversation
• Conversation state not found
• Item not found in turn state

The system had substantial free RAM, so this was not a machine-wide out-of-memory event.

Root-cause boundary

The evidence supports a renderer reload/recovery, not a full app restart or GPU-process crash. Text selection is the observed trigger, but the available evidence does not prove whether the underlying cause is selection/drag event handling, renderer memory pressure, or conversation-state desynchronization.

Related issues

• #29987 reports repeated drag actions, including text selection, causing restarts on macOS.
• #24263 reports a Windows renderer reload followed by turn-state desynchronization, but without this text-selection trigger.

Additional information

No session transcript, raw log, local filesystem path, account identifier, or source code is attached because those artifacts can contain private conversation data.