[Windows] Floating pet becomes undraggable after the first drag
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.825.6671.0
What subscription do you have?
Plus
What platform is your computer?
Windows (x64; exact OS build not recorded)
What issue are you seeing?
In the Windows Codex desktop app, a floating pet can be dragged immediately after it is selected or woken. After the first drag is released, the pet remains visible but no longer responds to physical mouse dragging. Switching to another built-in or custom pet does not restore dragging; the other pets are also affected. The custom pet asset is not the sole cause because built-in pets reproduce the problem. No screenshot or personal photo is attached.
What steps can reproduce the bug?
- Open Settings > Pets.
- Select a built-in or custom pet and wake it.
- Drag the floating pet once with the left mouse button, then release.
- Try to drag it again.
- Switch to another pet and try dragging it.
The issue reproduces consistently after the first release. Restarting the app and testing standard display scaling did not resolve it. A programmatic/synthetic drag can move the overlay, while the physical mouse path becomes ineffective, suggesting that the native input region or click-through state is not restored after the first drag.
What is the expected behavior?
The floating pet should remain draggable after every mouse release and after switching between pets.
Additional information
This appears to affect both built-in and custom pets on Windows. Please investigate the overlay's native input hit region / mouse passthrough state after drag end. Reproduced without attaching local logs or personal images.
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 floating-pet drag sequence in Settings > Pets, including switching pets and comparing physical with synthetic dragging. Trace the overlay's native input hit region and mouse passthrough state after drag end; done means built-in and custom pets remain draggable after every release and pet switch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop-dev, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100