[Windows][Voice] Floating orb and all three controls remain click-through after app restart

Environment

• Windows desktop app; installed package OpenAI.Codex version 26.901.6511.0 (verified locally).
• Observed September 6, 2026.
• Foreground application: Google Chrome.

What happens

After starting voice mode and switching from the main app to Chrome, the floating blue voice orb and its microphone, end-call (X), and speaker controls remain visible, but they cannot be clicked or dragged. Mouse input passes through to Chrome: dragging over the orb can highlight webpage text underneath it.

The user fully quit and restarted the desktop app and reproduced the same issue. Restarting did not restore interaction.

Steps to reproduce

1. Start a voice conversation in the Windows desktop app.
2. Switch to Google Chrome so the floating voice orb appears over the browser.
3. Attempt to drag the blue orb.
4. Attempt to click the microphone, X, and speaker controls beneath it.
5. Observe that the underlying webpage receives the mouse input; text underneath can be selected while the overlay stays in place.
6. Fully quit and restart the desktop app, start voice again, and repeat. The issue persists.

Expected behavior

The orb should be draggable, and each visible voice control should receive clicks and operate the active voice session. Interaction with those visible regions should not pass through to the application underneath.

Diagnostics and related reports

The interaction and restart results above were reported directly by the user. A supplied screenshot confirms the visible orb and three controls over Chrome. A targeted read-only search of the current desktop logs did not find an explicit overlay/drag/input-shape error; the root cause is unconfirmed.

Possibly related:

• #40239: voice buttons do not trigger actions, but that report says clicking the orb and hovering controls work. Here, the orb and controls pass input through to Chrome.
• #42862: voice orb cannot be dragged, with desktop/taskbar input disruption. Here, the confirmed symptom is input passing through the overlay to Chrome.
• #41465: a floating pet remains click-through; this report concerns the voice overlay.

Please investigate voice-overlay hit testing and pointer-interactivity transitions when the main app loses focus. This report was prepared with AI assistance and submitted at the affected user's request.

No file or test is named. Reproduce on Windows, then trace voice-overlay hit testing and pointer-interactivity transitions when the main app loses focus, comparing the related reports listed in the issue. Done means the orb remains draggable and all three controls receive input after switching to Chrome and restarting the app.