Windows voice orb snaps to a fixed position, cannot be dragged, and desktop/taskbar clicks stop working
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Environment
- Windows desktop app, installed package version: 26.901.4073.0 (verified from the running executable path).
- Observed on September 4, 2026; the user reports this has persisted for several days.
User-observed behavior
During an active voice conversation, opening the Codex main window makes the floating voice orb return to its default position or jump toward the middle of the screen. It then cannot be dragged. At times, desktop icons and other applications' taskbar icons also stop responding to clicks, while the Codex taskbar icon remains usable. The user also reported unresponsive voice controls.
Using Windows Show desktop restores clicking on other applications, but the voice orb still cannot be dragged.
Reproduction observed by the user
- Start a voice conversation in the Windows desktop app.
- Open or bring up the Codex main window.
- Observe the voice orb reposition itself and attempt to drag it.
- When desktop/taskbar clicking becomes affected, use Show desktop: other applications become clickable again, but dragging the orb remains broken.
Troubleshooting already tried
- Exiting and reopening the application did not resolve the problem.
- Pressing Esc did not restore desktop/taskbar interaction.
- Exiting a third-party desktop assistant did not resolve the issue.
- Show desktop only partially restores interaction as described above.
Read-only diagnostic findings
The desktop logs for the affected voice session show that the avatar overlay loaded successfully. They also contain repeated directory-read failures while starting visualization diff snapshots and two primary-window ResizeObserver loop errors. These are observations only; no causal connection to dragging has been established. A targeted search did not find direct drag/hit-test failure records or a corresponding application crash. No raw logs, account identifiers, conversation contents, or private local paths are attached.
Expected behavior
The voice orb should be movable and its overlay should not prevent clicking desktop or taskbar icons.
Related reports
- #41262: voice orb cannot be dragged over Shadow PC. This report does not require that remote/fullscreen setup.
- #41465: floating pet is click-through. This report also includes blocked clicks on other applications, so an identical root cause has not been established.
Please investigate overlay positioning and mouse-input routing when activating the main window during voice. Is there a known workaround or a fixed desktop version?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows desktop app steps during an active voice conversation: open the main window, move the voice orb, and test desktop and taskbar clicks. Investigate overlay positioning and mouse-input routing, using the reported ResizeObserver errors and diagnostic findings as observations rather than established causes. Done means the orb remains movable and its overlay does not block other desktop or taskbar interactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100